Creator-owned software for selling private media.
A platform can decide, on a Tuesday, that your business is no longer welcome on it. It can change the terms, hold the payout, lose the appeal, and give you no one to speak to. Erycina exists because the people that happens to should be able to own the machine instead.
Erycina is software you run. It holds a catalogue, sells access to it, verifies what a payment provider tells it, and delivers media to people who are entitled to it. It is MIT licensed. Fork it, host it, sell hosting for it.
Control also means responsibility
When you use a hosted platform, the operator absorbs a great deal on your behalf: infrastructure, security, moderation, payment relationships, compliance, the 2 a.m. outage. Erycina cannot hand those to anyone. When you run it, you are operating the service.
That is the honest trade, and it belongs on the front page rather than in a footnote halfway through an install guide.
Erycina provides software. It does not provide legal advice, compliance certification, or immunity from liability.
Before you deploy anything, read Self-hosting. There is an interactive checklist that takes a description of the deployment you have in mind and tells you which areas it raises.
What it does
- Offers and orders. A server-owned, immutable offer fixes the amount, currency, and content class before any checkout begins. The client never supplies the price.
- Payments. A provider-neutral driver boundary with CCBill, Segpay, Verotel, and Stripe adapters. The adult-content processors are first-class targets, not an afterthought bolted onto a Stripe integration. See Payments.
- Entitlements. Erycina never mints access itself. A verified provider event becomes a normalised payment fact; Heimdall alone grants, refreshes, and revokes the signed claims that unlock media.
- Media policy. Originals and protected derivatives are structurally separated from anything publishable. The public tree is the only thing that ships.
- Relationships. Terminus tracks conversations, boundaries, and an enforcement ladder, and speaks as itself when it takes over. It never sends anything an operator has not approved.
Where the project actually is
Erycina is not finished, and there is nothing to be gained from pretending otherwise on its own website.
Working today: the daemon, the media ingest pipeline, the tenant projection, the payment-driver scaffold with focused contract tests, and Terminus.
Not built yet: production notification ingress, immutable order and payment-fact persistence, merchant onboarding, secret injection, the Heimdall intake, and provider-specific integration tests. Nobody should be taking real money through this yet.
The first tenant is live and the platform underneath it is still being assembled. That is the true state of things, and this page will be updated when it changes rather than when it would be convenient.
Source
The canonical repository is self-hosted Forgejo at git.erycina.org. That is deliberate: a project telling creators to own their infrastructure should not keep its own source on someone else’s platform.