Self-hosted deployment
Floyant is self-hostable from day one. Exact packaging and installation requirements will be published at release.
Hosting and operations
Self-hostable from day one: run Floyant on infrastructure you control. A managed hosted option is coming too — entirely optional.
What it gives you
- Run on your own infrastructure — your servers, your domain, your rules
- Environments isolate drafts, previews, and live apps
- Self-hosting is a day-one capability — fully in your hands
- Operations settings — schedules, retention, storage — live in the app definition
A worked concept
A team deploys Floyant on their own infrastructure, publishes their reconciliation app under their own domain, and iterates in draft — with a managed hosted option available when they prefer it.
How it works
Optional managed hosting
A managed hosted service on our infrastructure is also coming as an option for teams that prefer it — with platform-managed URLs and deferred custom domains. Optional always — timing announced at release.
Operations in the definition
Scheduling, retention, and run limits are declared alongside the app, so operations travel with the definition.
Worth knowing
- Self-hosted operators manage their own infrastructure, backups, and upgrades
- Self-hosting gives you full operational control — your apps run on the Floyant platform, on infrastructure you own
- Platform-managed custom domains are deferred on the managed offering; self-hosted deployments use your own domain and infrastructure
- SLA and certification details will be published at launch