# Stackap

> Stackap is a platform you own: git deploys, HTTPS, Postgres, storage, cron jobs and encrypted backups on one server, operated by your coding agent.

Stackap is an early-access, invite-only platform that runs on one server the owner controls and does the job of a git host, a deploy platform, a Postgres/storage backend, a scheduler and a backup system. The home page and the pages below describe it; figures on them are measurements from the platform's own tests and first migration.

## The home page, section by section

- [The short version](https://www.stackap.com/#the-short-version): If you read nothing else, read this.
- [What it is](https://www.stackap.com/#what-it-is): One server that does the job of a whole stack.
- [Why one stack](https://www.stackap.com/#the-problem): The cost of assembling a platform.
- [Why it exists](https://www.stackap.com/#why-it-exists): Because the economics of building platforms changed.
- [How it works](https://www.stackap.com/#how-it-works): From git push to live, step by step.
- [What is in the box](https://www.stackap.com/#whats-in-the-box): Every part, and what it really does.
- [Multi-tenant](https://www.stackap.com/#multi-tenant): One box, many organizations, solid walls.
- [Security](https://www.stackap.com/#security): What is locked, and how.
- [Proof](https://www.stackap.com/#proof): The first move: a real site, real data, real visitors.
- [Benefits](https://www.stackap.com/#benefits): What owning your stack gives you.
- [Early access](https://www.stackap.com/#early-access): Invite-only, and built with its first teams.
- [Who it is for](https://www.stackap.com/#who-its-for): The teams it fits best.
- [What is next](https://www.stackap.com/#roadmap): Where it is going.
- [Get access](https://www.stackap.com/#get-access): Ask for an invitation.

## Other pages

### Start here

- [Get started](https://www.stackap.com/get-started/): How to start on Stackap: get an invitation, receive your organization and token, hand a prompt to your coding agent, and see your app live.

### Product

- [Agent-first infrastructure](https://www.stackap.com/product/agent-first-infrastructure/): What agent-operable infrastructure means in practice at Stackap: commands, an HTTP API and plain-text docs an agent can use without a human in the loop.
- [Backups](https://www.stackap.com/product/backups/): How Stackap backs up databases and repositories to a bucket you own, encrypts them, and proves they restore, plus the gaps that remain.
- [Cron jobs](https://www.stackap.com/product/cron-jobs/): How Stackap runs scheduled jobs by calling a path on your app, imports vercel.json crons, records every run, and what the schedule semantics are.
- [Databases](https://www.stackap.com/product/databases/): How Stackap gives each project its own Postgres database and role, a Supabase-compatible data API, a table browser, and what it does not yet offer.
- [Deployments](https://www.stackap.com/product/deployments/): How Stackap deployments work: a git push is built into a Docker image, health-checked beside the old version, and only then switched live.
- [Domains](https://www.stackap.com/product/domains/): How Stackap attaches custom domains: one DNS record you create, a DNS check before issuing a certificate, automatic HTTPS, and expiry monitoring.
- [Environment variables](https://www.stackap.com/product/environment-variables/): How Stackap stores secrets: AES-256-GCM encryption bound to project and name, values masked when listed, stdin-only input, and how build-time values work.
- [Logs](https://www.stackap.com/product/logs/): How to read Stackap build logs and live runtime logs from the CLI or API, the size limits and rotation, and what is not collected.
- [Monitoring](https://www.stackap.com/product/monitoring/): The checks Stackap runs on itself, how alerts reach Telegram, the per-project load-time metrics, and the blind spot of a monitor on the same machine.
- [Rollbacks](https://www.stackap.com/product/rollbacks/): A Stackap rollback re-activates the previous deployment with one command, health-checking it first. What it restores, and what it cannot.
- [Scaling](https://www.stackap.com/product/scaling/): How Stackap scales an app by running 1 to 8 copies behind a load balancer on one server, the measured throughput, and what multi-server scaling still lacks.
- [Storage](https://www.stackap.com/product/storage/): How Stackap stores uploaded files in a Cloudflare R2 bucket you own, served by the open-source Supabase storage service, and what is verified so far.

### Solutions

- [Agencies](https://www.stackap.com/solutions/agencies/): How an agency can host several clients' apps on one Stackap server with separate organizations, and why tenant code is not yet sandboxed.
- [AI app deployment](https://www.stackap.com/solutions/ai-app-deployment/): How to deploy an app built with a coding agent: the commands an agent runs on Stackap, what a person still approves, and where it falls short.
- [Production AI apps](https://www.stackap.com/solutions/production-ai-apps/): What Stackap offers an app that calls model APIs: secret handling, logs, rollback and cron, and what it does not, such as GPUs, queues and long jobs.
- [SaaS](https://www.stackap.com/solutions/saas/): What Stackap hosts for a multi-tenant SaaS, why tenant isolation inside your app stays your job, and the single-server limits that matter at scale.
- [Solo founders](https://www.stackap.com/solutions/solo-founders/): How a solo founder running several products uses one Stackap server: one bill, one backup system, alerts to a phone, and the hours of upkeep it costs.
- [Startups](https://www.stackap.com/solutions/startups/): Where Stackap fits an early-stage startup, where it does not, and the questions a customer security review will ask that it cannot yet answer.
- [Vibe coding](https://www.stackap.com/solutions/vibe-coding/): For people building apps by directing an AI coding agent: how Stackap hosting fits, the terminal and DNS steps you still meet, and the safe habits to set.
- [Web apps](https://www.stackap.com/solutions/web-apps/): A map of the pieces of an ordinary web app, front end, API, database, files, cron and domain, to what Stackap provides and what you bring.

### Frameworks

- [Astro](https://www.stackap.com/frameworks/astro/): How Stackap builds a static Astro site and serves it from nginx with real 404 pages, and why Astro with a server adapter is not treated as static.
- [Docusaurus](https://www.stackap.com/frameworks/docusaurus/): How Stackap builds a Docusaurus documentation site and serves the build folder with a real 404 page, and the baseUrl setting that most often breaks it.
- [Eleventy](https://www.stackap.com/frameworks/eleventy/): How Stackap builds an Eleventy site and serves the _site folder, and why a project with no build script in package.json is not recognized.
- [Gatsby](https://www.stackap.com/frameworks/gatsby/): How Stackap builds a Gatsby site and serves its public folder from nginx with real 404s, what Gatsby features need a server, and what is untested.
- [Next.js](https://www.stackap.com/frameworks/nextjs/): How Stackap detects a Next.js project, the container it generates, how public and secret variables are handled, and what has been measured.
- [Node.js](https://www.stackap.com/frameworks/nodejs/): How Stackap runs a Node.js app that has a start script: the generated image, the PORT contract, health checks and what is not supported.
- [Nuxt](https://www.stackap.com/frameworks/nuxt/): Stackap does not recognize Nuxt by name. Why a Nuxt project skips the static path, how a start script changes that, and the untested caveats.
- [Python](https://www.stackap.com/frameworks/python/): Stackap has no Python support of its own. A Python app can run only if you provide a Dockerfile that listens on PORT, which is untested.
- [React](https://www.stackap.com/frameworks/react/): How a React app is served on Stackap: static single-page builds with client-side routing work, server components and server rendering do not.
- [Remix](https://www.stackap.com/frameworks/remix/): Stackap does not recognize Remix by name. What its detection does with a Remix project, when a start script lets it run as Node, and what is untested.
- [Plain static sites](https://www.stackap.com/frameworks/static-sites/): How Stackap serves a repository that is already a finished site, with an index.html at the root and nothing to build, and what is stripped from the image.
- [SvelteKit](https://www.stackap.com/frameworks/sveltekit/): Stackap does not recognize SvelteKit by name. How its detection treats the dependency, using the Node adapter with a start script, and what is untested.
- [Vite and React single-page apps](https://www.stackap.com/frameworks/vite/): How Stackap builds Vite, Create React App, Vue CLI and Parcel single-page apps and serves them from nginx with a fallback to index.html.
- [VitePress](https://www.stackap.com/frameworks/vitepress/): How Stackap builds a VitePress site from .vitepress/dist, and why the default docs:build script name means you must add a build script first.

### Deploy guides

- [Deploy an Astro site](https://www.stackap.com/deploy/deploy-astro/): Step by step: deploy a static Astro site to Stackap, with real 404 pages, build-time image handling and the server-adapter caveat.
- [Deploy a Next.js app](https://www.stackap.com/deploy/deploy-nextjs/): How to deploy a Next.js app to a server you own: git push, public build variables, a custom domain and a one-command rollback. Step by step.
- [Deploy a Node.js API](https://www.stackap.com/deploy/deploy-nodejs/): Step by step: deploy a Node.js API with a start script to Stackap, with the PORT contract, a health path, secrets and a database.
- [Deploy a React app](https://www.stackap.com/deploy/deploy-react/): Step by step: deploy a React single-page app to Stackap, the router and base-path settings that matter, and how to tell Vite from Create React App.
- [Deploy a Vite app](https://www.stackap.com/deploy/deploy-vite/): Step by step: deploy a Vite or Create React App single-page app to Stackap, with the index.html fallback, build-time variables and a custom domain.

### Compare

- [Heroku alternative](https://www.stackap.com/compare/heroku-alternative/): A Heroku alternative with git-push deploys, Postgres and cron on your own server. Procfile and dynos versus containers; add-ons versus built-in services.
- [Railway alternative](https://www.stackap.com/compare/railway-alternative/): A Railway alternative for a fixed server cost: one container and a private Postgres per project, with no multi-service canvas. What you give up.
- [Railway vs Stackap](https://www.stackap.com/compare/railway-vs-stackap/): A direct comparison of Railway and Stackap on billing, project shape, databases, scaling and operations, written to say where each is the better pick.
- [Render alternative](https://www.stackap.com/compare/render-alternative/): A Render alternative for web services, static sites and cron jobs on a server you own: what maps across, what does not, and what a move involves.
- [Supabase alternative](https://www.stackap.com/compare/supabase-alternative/): A Supabase alternative for the data side: tables, rows, the data API and storage carry over; sign-in, realtime and edge functions do not. A feature checklist.
- [Supabase vs Stackap](https://www.stackap.com/compare/supabase-vs-stackap/): A factual comparison of Supabase and Stackap for Postgres, storage and APIs: what each provides, what Stackap lacks, and when each is the better choice.
- [Vercel alternative](https://www.stackap.com/compare/vercel-alternative/): A Vercel alternative that runs on a server you own. Check what you rely on first: previews, edge and functions do not move; git deploys, cron and domains do.
- [Vercel and Supabase alternative](https://www.stackap.com/compare/vercel-and-supabase-alternative/): Stackap does the deploy half of Vercel and the Postgres and storage half of Supabase on one server you own. What it replaces, and what it does not.
- [Vercel vs Stackap](https://www.stackap.com/compare/vercel-vs-stackap/): A factual comparison of Vercel and Stackap for deploying web apps: what each handles, who runs the servers, and where the trade-offs sit.

### Migrate

- [Migrate from Heroku](https://www.stackap.com/migrate/from-heroku/): How to move a Heroku app to Stackap: map the Procfile to a start script, config vars to environment variables, Heroku Postgres to a project database.
- [Migrate from Railway](https://www.stackap.com/migrate/from-railway/): How to move an app from Railway to Stackap: split a multi-service project, copy variables and the Postgres data, and handle private networking.
- [Migrate from Render](https://www.stackap.com/migrate/from-render/): How to move web services and static sites from Render to Stackap: environment groups, the Postgres dump, cron jobs, and the persistent disk question.
- [Migrate from Supabase](https://www.stackap.com/migrate/from-supabase/): Moving a Supabase database and storage onto Stackap: the tables and rows that copy, the functions that do not, and sign-in that blocks the move.
- [Migrate from Vercel and Supabase](https://www.stackap.com/migrate/from-vercel-and-supabase/): The steps, the inventory and the known gaps for moving an app from Vercel and Supabase onto Stackap, based on the first real move.
- [Migrate from Vercel](https://www.stackap.com/migrate/from-vercel/): Moving an app from Vercel to Stackap when the database stays put: variables, crons, domain and the Vercel-only settings that need recreating.

### Developers

- [Agent documentation](https://www.stackap.com/developers/agent-docs/): Plain-text Stackap documentation for coding agents: the canonical definition, llms.txt files, authentication, and the HTTP routes that exist today.
- [API reference](https://www.stackap.com/developers/api/): Every Stackap HTTP route that exists today, with its request body, what it returns, who may call it and how errors look.
- [Changelog](https://www.stackap.com/developers/changelog/): What has shipped in Stackap, by date, written from the verified state of the platform, with nothing listed that is only planned.
- [CLI reference](https://www.stackap.com/developers/cli/): Every command in the Stackap command-line tool, with what it does, how it takes secrets, how it signals failure, and what is not built yet.
- [Documentation](https://www.stackap.com/developers/docs/): An index of Stackap documentation by task: shipping an app, operating it and moving an existing one, with what does not exist yet.

### Resources

- [FAQ](https://www.stackap.com/resources/faq/): Straight answers about Stackap: what happens if the server dies, leaving, Next.js, Supabase compatibility, cost, security and whether it is production-ready.
- [Glossary](https://www.stackap.com/resources/glossary/): Plain-English definitions of the terms used across Stackap: control plane, project, organization, health check, rollback, PostgREST, R2 and more.

### Company

- [About](https://www.stackap.com/company/about/): Why Stackap exists: software creation changed, infrastructure operation did not, and one founder built a platform so agents can do the operating.
- [Contact](https://www.stackap.com/company/contact/): Ask for an early-access invitation to Stackap: tell us what you run and we will reply by email with a straight answer about whether it fits.
- [Mission](https://www.stackap.com/company/mission/): Stackap's mission and the four engineering principles behind it: do not send the human to a setting, courier, or diagnosis; documentation bugs are real bugs.
- [Privacy](https://www.stackap.com/company/privacy/): What happens to the details you send through the Stackap contact form, what the website does and does not track, and how to ask us to delete your message.
- [Reliability](https://www.stackap.com/company/reliability/): How Stackap keeps a site up and recovers: health-checked deploys, one-command rollback, monitoring and alerts, replicas, and backups that are restore-verified.
- [Roadmap](https://www.stackap.com/company/roadmap/): Where Stackap is going: hosting today, then a phone service and an email service, then financial services, all in one place that an agent can operate.
- [Security](https://www.stackap.com/company/security/): The security controls built into Stackap today, how the walls between organizations are tested, and how regulated workloads are handled in early access.

### Pricing

- [Pricing](https://www.stackap.com/pricing/): Stackap is in invite-only early access. How pricing works today, what is included, and how to ask for an invitation.

## Optional

- [Full text of the page as Markdown](https://www.stackap.com/llms-full.txt)
- [Sitemap](https://www.stackap.com/sitemap.xml)
- Contact: hi@stackap.com