Sapilon becomes publicly available on 1 December 2026: 42 days to go. The core goes open source the same day →

Product

AWS-native deployment

Ship to real AWS across Build, Rehearsal, and Live Server environments, with cost visibility and no lock-in.

Real AWS, multi-environment

Sapilon provisions and runs production-grade AWS infrastructure for your project, with separate Build, Rehearsal, and Live Server environments. Infrastructure is treated as part of the product, not an afterthought. You never open a console or wire up a pipeline.

Three ways to run it, suggested for you

Answer two questions (how bad would a day of downtime be, and does the app hold health, payment or children’s information?) and Sapilon suggests one of three architectures. Essential runs everything on one server. Balanced adds a Rehearsal Server that runs when you need it. Dedicated gives the app everything of its own, in an AWS account kept apart from every other project. What each costs a month is published, near cost, on the hosting prices page.

Your own web address

Every web app on a server shares one address, each on its own path. Add your own domain on the Publish page and create the two records it gives you; the Sapilon address keeps working the whole time.

No lock-in

The web and api platform your software is built on is open source. With plain Git repositories and standard AWS services, you can always take your software and run it elsewhere. Managed services (sign-in, users and roles, files, notifications, integrations, backups) are conveniences, not cages.

Your own AWS account (Enterprise)

Teams with an existing AWS estate or their own compliance boundary can have Sapilon deploy into their AWS account instead of ours. Available on Enterprise plans, on request.

See it on your own software

Publicly available on 1 December 2026 42 days to go