Questions people ask

Your sites are down until you restore, and restoring is built for it: databases and repositories are backed up daily to a bucket in a different company's cloud, encrypted, and restore-tested, and a restore onto a separate machine from only the bucket and the master key has been proven. A full rebuild drill on a fresh machine and a standby server are on the roadmap.

Yes, and that is a design goal. Your data is in standard Postgres that you can dump with ordinary tools. Your files are in your own bucket. Your applications are containers and plain git repositories. The Supabase-compatible layer means application code does not need to change on the way out any more than it did on the way in.

No. Any application that can run in a Docker container works: give it a Dockerfile that listens on the port Stackap provides. Next.js is special only in that Stackap will generate the Dockerfile for you if you do not have one. This very page is a plain static site served by a small web server in a container.

For the parts we use, very. The data API is PostgREST, the same engine Supabase uses, and file storage is the official Supabase storage service. An application using the standard JavaScript client was tested against the kinds of queries a large production codebase makes. What it does not include is Supabase's authentication service, realtime subscriptions or edge functions; applications that depend on those would need work.

Early access runs on a server in Germany. The location is a choice, not a constraint: visitors in North America see a little extra latency, and a server in the United States is a matter of provisioning another machine and restoring from backup.

For the large Next.js site, the build was about 96 seconds, and the whole path from push to live was a couple of minutes. A static site like this one builds in a few seconds.

You need to be comfortable with a terminal, SSH and DNS records. You do not need to hand-configure certificates, proxies, container networking or backup scripts, because those are the parts Stackap does. If you can follow a hosting provider's setup guide, you can run it. If you would rather not, the platform is also designed to be driven by an AI coding assistant.

Environment variables and database connection strings are encrypted at rest and bound to their project and name. They are never shown back in plain text and are handed to containers through a private file rather than the command line. Access tokens are stored only as one-way hashes. The master key that unlocks everything lives outside the server's own database; if it is lost, encrypted variables and backups cannot be recovered, so keep a copy in a password manager.

Yes. Attach the domain to a project, create the single DNS record Stackap shows you, and routing and the certificate switch on by themselves once DNS is correct. Lower the record's cache lifetime a day before any production switch. This site's bare domain redirects to the www address.

Stackap is in invite-only early access, and terms are arranged with each team. See pricing for how that works, and ask for an invitation to start the conversation.

That is the plan. Hosting comes first and is in early access today. A phone service and an email service are in development next, then financial services, so the operating side of a small business can live in one place that an agent can run. None of the three is available yet; the roadmap says what is planned and in what order.

Stackap is the founder's own software and is not publicly distributed yet. Access is by invitation while the remaining gaps are closed. If you are interested, the contact page says how to ask.

Tools such as Coolify and Dokploy cover deploying applications and databases on your own server, and they are worth a look. Stackap's particular combination is the part that surrounds the deploy: Supabase-compatible data and storage layers, verified encrypted backups with restore testing, a built-in scheduler that imports vercel.json , and walled multi-tenant organizations. We have not benchmarked against them and do not claim to be better at what they do.

Stackap is in early access: it serves a real public website today and has passed the checks described in the proof section , and a limited number of teams are being invited with hands-on onboarding. It runs on one server, so whether it fits depends on what a bad hour of downtime would cost you. The early-access page lists exactly what is included.

Yes, and it is how it was built. Everything the dashboard can do is an authenticated API call, the command-line tool wraps the same API, and output is plain text. That makes it straightforward for scripts and coding assistants to deploy, read logs, change variables and roll back.