Projects
We don’t have your code. We run it.
A Project is one application: its components, and everything they need to run. Connect your repository and Sarpius builds it, routes it, gives it data and storage, and shows you exactly what it costs per minute. Your repository stays yours.
Free to start, no card required.
Anatomy
This is a Project.
One application, its components, and the infrastructure they share. Everything below was created by connecting one repository.
Frontend
SvelteKit
deployed
API
PHP 8.3
deployed
Worker
Java 21
deployed
What you get
Everything the app needs, in one place.
Git deploys and containers
Push to your branch and the component rebuilds in a sandboxed build, then rolls out. Start it, stop it, or roll back to an earlier deploy. Scheduled jobs run on the same artefact and the same secrets.
Databases, Redis and storage
Managed PostgreSQL, MariaDB and Redis, plus S3-compatible buckets. Create one in the Project and its connection variables are injected into the components that use it. Unlink it and exactly those variables are removed again.
Routing, TLS, logs and costs
A subdomain the moment you deploy, your own domain when you are ready, with certificates issued and renewed for you. Logs and health per component, a live per-minute meter, and a spend cap you set yourself.
Serverless Functions
Event-driven functions running beside your deployed components. Same Project, same permissions, same logs, same spend cap and the same billing boundary.
How you work
Your Git, your editor, your agent.
Sarpius does not ask you to move into a new environment. Keep the tools you already use; the Project is what runs on the other end.
Your own Git
GitHub, GitLab, Gitea, Bitbucket or plain Git. A push is the deploy trigger; there is nothing else to run.
Your own editor
Work locally in the editor you already have. Nothing about a Project requires a browser IDE.
Your own agent
Drive the whole lifecycle from CI, your own tooling or an AI assistant over MCP, with the same permissions and the same spend caps as the console.
No lock-in
Your repo, your data, your exit.
We don’t have your code. We run it.
Connect your own repository and it stays yours, on your own git host, under your own account. We build and host what is already yours. Start from a template instead and you can point the component at your own repository whenever you want.
PROJECT MIGRATION BUNDLE
Leaving should be a download, not a support ticket. The bundle hands you everything the platform was holding:
- Git URL and the exact commit SHA of what is running
- The built front-end and static output
- Back-end files and runtime configuration
- A SQL dump of every database in the Project
- The contents of your storage buckets, with checksums; an oversized bucket gets a read-only key
- Routes, build settings and restart instructions
Downloaded from your account behind two-factor authentication, never mailed.
Advanced
The infrastructure underneath, when you want it.
A Project wires these for you. They each have their own console and their own page for when you want to go a level down.
Start with one repository.
Connect it and Sarpius takes it from there.