The questions we get asked most

What is Sarpius, and who is it for?

Sarpius takes your code and runs it in production, so you do not manage servers, networking or deploys yourself. You connect a repository, the platform detects what is in it, provisions what it needs and deploys it.

The unit you work in is a Project: one application made of multiple components, a front-end, a back-end, workers, plus the databases, storage and routing they share. Built for developers and small teams who want clarity rather than knobs.

How is it different from Vercel, Railway or Render?

Same idea, different home. Sarpius runs entirely on our own hardware in the Netherlands, so your data stays under European jurisdiction and you are not depending on a US cloud provider.

Billing is per minute from a wallet, so you pay for what actually runs instead of a monthly slab. And we publish what we cannot do yet, which is the other half of the difference.

How do I get started?

No waitlist and no invite. Sign up with an email address, connect a repository and deploy your first app for free.

Every app gets an automatically generated subdomain on sarpius.app with a certificate, so you have a working URL before you own a domain.

How does pricing work?

Your first app is free and stays free: one small container, 10 GB of bandwidth, a free subdomain with TLS, no credit card and no trial clock.

Beyond that, everything is metered per minute from your wallet:

Each additional app

EUR 4,99 / month

Bandwidth above the 10 GB per app

EUR 0,05 / GB

Custom domain

EUR 1,99 / month

Direct-origin routing per custom domain

+ EUR 4,99 / month

Each extra replica under autoscaling

about EUR 2,50 / month

These are the rates the biller charges and they exclude VAT; the calculators on the pricing page add it. Because it is metered per minute, an app you stop billing stops costing, without a cancellation.

Which languages and frameworks are supported?

If it runs in a container, it runs on Sarpius. On top of that the connect-a-repository wizard recognises 45 frameworks and runtimes and configures the build, the port and the environment variables for you.

Among them: Next.js, Nuxt, SvelteKit, Astro, Angular, React, Vue, Vite and Remix-style React Router; Laravel, Symfony, WordPress and plain PHP; Express, Fastify, NestJS, Hono and Node.js; Django, Flask, FastAPI, Streamlit and Gradio; Go, Java on Maven or Gradle, .NET; Hugo, Eleventy, Docusaurus, MkDocs and static sites; plus Strapi, PocketBase and Discord bots.

Missing your stack? Ask in Discord. It goes on the public list as planned, and it only moves to supported once a real repository has been detected, built and deployed.

What databases can I run?

Three engines, reachable over TLS with any standard client, provisioned and linked to your app from inside the Project.

More engines arrive through the same ongoing track as frameworks: something is listed once a real database of it has been provisioned, linked and used, not when the code path exists.

PostgreSQL 16

Relational, full SQL. Free shared tier of 500 MB and 5 connections; dedicated from EUR 2,99 / month with 10 GB included.

Redis

In-memory key/value and pub/sub. Dedicated, 512 MB included, persistence is opt-in.

MariaDB

MySQL-compatible relational. Dedicated, 10 GB included, 1 vCPU and 1 GB RAM.

Where is my data stored?

On our own infrastructure in the Netherlands. Your data stays within the EU, under the GDPR, and never touches a non-EU cloud provider. That is the reason the platform exists, not a checkbox on it.

The honest addition: everything runs in a single location today. An outage that takes that location down takes your application with it. A second, genuinely independent zone is on the roadmap, and we will publish the failover test when it exists.

What happens if I lose data? Do you take backups?

Shared और dedicated PostgreSQL के लिए, और dedicated Redis और MariaDB के लिए, हाँ, और आप इसे खुद करते हैं: एक restore point बनाएँ, या रात में अपने आप बनने वाला एक point चालू करें, और अपने database को console से बिना ticket के वापस लाएँ। हर restore पहले मौजूदा स्थिति को एक safety point के तौर पर सेव करता है, इसलिए एक restore खुद भी वापस पलटाया जा सकता है। Dedicated PostgreSQL 16 पर point-in-time recovery भी चालू की जा सकती है, जिससे सिर्फ आख़िरी restore point पर नहीं बल्कि पिछले 7 दिनों में किसी भी सेकंड पर वापस जाया जा सकता है।

जो अभी तक मौजूद नहीं है: buckets के लिए आप खुद वापस लगा सकें ऐसे restore points, और एक दूसरी स्वतंत्र location या zone। इसके अलावा Sarpius हर रात सभी object-storage buckets, platform databases और platform configuration की client-side एन्क्रिप्टेड off-site प्रति बनाता है, ताकि आपदा के बाद platform को वापस लाया जा सके; यह प्रति-ग्राहक restore service नहीं है। जो कवर नहीं है, उसके लिए अपना खुद का export या dump रखें।

Can I get my application out again?

Yes, and that is deliberate. Your code lives in your own git repository; we never become the only copy of it.

Databases are ordinary PostgreSQL, Redis and MariaDB reachable with standard clients, so a standard dump is a standard dump. Owning your whole application is only acceptable if you can walk out with it.

What if I need help or hit a problem?

Ask in Discord, which is the fastest line to us, or open a support ticket and we will pick it up.

For anything that looks like an outage, the status page carries live uptime per component and the history of every incident we have handled, including what went wrong.

What are you building next?

In order: the numbers and recovery limits published up front, then Serverless Functions, then SarpiVault for secrets, then backup and restore as a real product, then a rebuilt SparxLite with free sizing alongside SparxCore cloud VMs, then customer cases, then a second independent zone.

The roadmap page carries the reasoning for that order and names what we fall short on today.