Skip to content

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

@matfire

Description

@matfire

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions