Stormkit

Stormkit deploys an application and hands it the surrounding pieces most projects end up assembling one service at a time. A single install script turns your own server into a platform with git push deploys, a preview address for every branch and custom domains with automatic TLS.

Runtimes come from mise, so Node, Go, Python, Ruby and anything else it supports will build, with system packages declared in a Nix flake and a start command for running a long-lived server in any language. Deployments can also arrive from the interface, a zip upload or the API, and status checks gate a publish.

The platform bundles services an application normally buys separately.

• Database: a PostgreSQL instance attaches to an environment and migrations run on deploy.
• Authentication: Stormkit Auth handles your end users with passwords, magic links, Google and X, and manages sessions.
• Email: a transactional mailer is wired to your own SMTP provider.
• Scheduled jobs: periodic triggers run without a separate cron machine.
• Analytics: server-side numbers are collected without depending on client tracking.
• Agent control: the platform is exposed over MCP, so a coding agent can provision, deploy, publish and read logs.

A managed cloud exists, but the full platform lives in the self-hosted install, since the database, Stormkit Auth, the OAuth 2.1 server and long-lived runtimes are self-hosted only. The Docker images need PostgreSQL and Redis alongside them. The project is open core, with a Community Edition under AGPL-3.0 and commercially licensed enterprise components.