There is no deploy button, and offering one before the platform is ready would be the least responsible thing this project could do.
Read Self-hosting before anything on this page. Not because of a legal formality — because the deployment decisions below are downstream of questions that page asks.
What exists today
An Erycina instance is a .NET daemon, a media ingest pipeline, a tenant data directory, and a static public projection served by a web server you control.
- The daemon serves local health and job endpoints. They are probes and direct operator controls, not a second dashboard authority.
- Tenant configuration, media, and public output are runtime data. They live outside the platform’s source tree, because a platform whose purpose is to acquire a second creator should not have its first one compiled into it.
- Typed operational state is published for operator tooling over CultMesh. It is a projection; it owns nothing.
Build and run instructions live with the source at git.erycina.org.
What does not exist yet
Trusted notification ingress, immutable order and payment-fact persistence, merchant onboarding, secret injection, registered provider notification endpoints, the Heimdall entitlement intake, and provider-specific integration tests.
Do not point a production instance at real money. The shipped configuration carries empty credential placeholders and that is the correct state for it to be in.
What you have to decide before it matters
These are yours regardless of how the software eventually packages itself.
- Where it runs, and who else has administrative access to that machine.
- How secrets reach it. Processor credentials never belong in your repository, and a self-hosted platform makes that your discipline rather than a vendor’s.
- What your backup scheme is, and whether you have tested a restore. An untested backup is a belief.
- What is public. Originals, protected derivatives, proof-of-age records, model releases, processor credentials, signed delivery tokens, and customer identity never enter a tenant’s public tree. Erycina treats everything in that tree as reviewed and deploys it verbatim.
- What happens on a bad day. Breach, seizure, deletion, a provider dropping you. Decide in advance who you would have to tell and how quickly.
The responsibility checklist will raise the ones your particular deployment makes sharper.