Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

define recurring billing strategy (not mandatory in self-hosted) #43

Open
matfire opened this issue Jan 16, 2024 · 0 comments
Open

define recurring billing strategy (not mandatory in self-hosted) #43

matfire opened this issue Jan 16, 2024 · 0 comments

Comments

@matfire
Copy link
Member

matfire commented Jan 16, 2024

RFC

Objective

  • Define short to medium strategy
  • Create small revenue stream for SASS version of Magiedit
  • Finance paid integrations and storage

Considerations

  • There is already a Stripe integration for "credits" that get used when using paid integrations (like OpenAI)
  • Ideally, this could switch to a monthly pay-to-use fee to simplify the billing process
  • This is a short to medium term discussion; there are things that need to be fixed before I consider truly charging users
  • It will consist of a free and pay-as-you-go plan
  • Reaching the end of the free plan will lock that functionality until the condition to meet it is met again
  • Obviously, you can self host the application and you won't have to pay a dime (but will have to provide your credentials for the paid integrations)

Free Plan

  • 10 image generations per month
  • 10 stored images
  • 10 articles

Pay as you go

  • 0.50€ per image - stored or generated - and article (after the free tier)

What do you think ?

Though this application was built mainly for me to help me writing articles, I would welcome your input in this.

@matfire matfire added this to magiedit Jan 16, 2024
@matfire matfire converted this from a draft issue Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant