Stackap

Site map

This is every page on Stackap, grouped by section, each with its one-line description.

Every page on Stackap, grouped by section. Home, pricing and get started sit outside the sections.

Product

• Product: What Stackap does. 24 pages on Stackap about product, with the details of how each part works today.
• 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.
• Automation and agents: The scheduled jobs and in-product AI agent inside Stackap Business, and how approvals, scoped tokens and idempotency are being applied to them.
• Backups: How Stackap backs up databases and repositories to a bucket you own, encrypts them, and proves they restore, plus the gaps that remain.
• Business: Stackap Business connects the lifecycle from lead to booking, job, payment, books and repeat customer in one system an agent can operate. In development.
• Cloud: Stackap Cloud is the build-and-run half of Stackap: git push to HTTPS, Postgres, storage, domains, cron, logs, backups and rollback, operated by your agent.
• Commerce and payments: Invoices, card checkout, refunds, worker payouts, e-commerce orders, print-on-demand fulfillment and business websites. Part of Stackap Business.
• Communications: SMS, email, voice, web chat and team messaging in one hub with a shared history per customer, plus an AI voice agent. Part of Stackap Business.
• CRM: The customer-management part of Stackap Business: clients, leads, deals, quotes and tasks, linked to bookings, payments and books. In development.
• 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: 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: How Stackap deployments work: a git push is built into a Docker image, health-checked beside the old version, and only then switched live.
• Documents and e-signatures: Create, send and sign documents with native e-signature, generate PDFs and keep files with the customer or worker they belong to. Stackap Business.
• 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: 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.
• Finance: A double-entry ledger with period close, bank reconciliation, financial statements and per-job profitability, posted from real payments. Stackap Business.
• 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.
• Marketing: Review requests and replies, a local SEO automation engine, SMS and email campaigns with opt-out, and lead attribution. Stackap Business.
• 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: A Stackap rollback re-activates the previous deployment with one command, health-checking it first. What it restores, and what it cannot.
• Sales: Quotes with public links, a deal pipeline, and follow-up jobs that chase leads, quotes and overdue payments. Part of Stackap Business. In development.
• 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.
• Scheduling and operations: Bookings with an availability engine, recurring schedules that generate themselves, jobs with checklists and photos, and crew check-in. Stackap Business.
• 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.
• Workforce and HR: Team members, applications, onboarding checklists, documents, performance reviews, commissions and payouts for crews and staff. Stackap Business.

Solutions

• Solutions: Who it is for. 8 pages on Stackap about solutions, with the details of how each part works today.
• 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: 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: 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: 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: 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: 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: 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: 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.

Industries

• Industries: Who Stackap Business is built around. 7 pages on Stackap about industries, with the details of how each part works today.
• Cleaning: What Stackap Business does for a cleaning company: guided intake, availability with travel buffers, recurring visits, crew check-in, pay and reviews.
• How to automate lead follow-up for a cleaning business: A follow-up sequence for cleaning leads: instant acknowledgement, a fast human touch, quote chasers, stop rules, consent for texting, and how to measure it.
• How to calculate cleaning job profitability: Work out what each cleaning job really earns: revenue less labor, travel, supplies and fees, with a worked example and the mistakes that hide losses.
• How to manage cleaning crews: Manage cleaning crews with standard checklists, clear onboarding, reliable check-in, quality checks and honest pay, so quality does not depend on who is on shift.
• How to reduce scheduling gaps and no-shows: Cut dead time and missed visits: travel buffers, clustering by area, time windows, two-step reminders, a clear cancellation policy and a way to fill open slots.
• How to schedule recurring cleaning clients: A practical method for scheduling weekly and biweekly cleaning clients: store the pattern, generate visits ahead, handle skips, keep one cleaner, protect margins.
• How to structure a CRM for a cleaning business: Set up CRM records for a cleaning company: clients, contacts, properties, service plans, visits, quotes and payments, with the fields that matter and what to skip.

Frameworks

• Frameworks: What Stackap recognizes. 14 pages on Stackap about frameworks, with the details of how each part works today.
• 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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 guides: How to deploy, step by step. 5 pages on Stackap about deploy guides, with the details of how each part works today.
• Deploy an Astro site: 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: 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: 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: 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: 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

• Compare: Stackap against the alternatives. 9 pages on Stackap about compare, with the details of how each part works today.
• 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: 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: 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: 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: 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: 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: 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: 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: 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: Moving to Stackap. 6 pages on Stackap about migrate, with the details of how each part works today.
• 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: 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: 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: 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: 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: Moving an app from Vercel to Stackap when the database stays put: variables, crons, domain and the Vercel-only settings that need recreating.

Developers

• Developers: Build with Stackap. 5 pages on Stackap about developers, with the details of how each part works today.
• Agent documentation: Plain-text Stackap documentation for coding agents: the canonical definition, llms.txt files, authentication, and the HTTP routes that exist today.
• API reference: Every Stackap HTTP route that exists today, with its request body, what it returns, who may call it and how errors look.
• 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: 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: An index of Stackap documentation by task: shipping an app, operating it and moving an existing one, with what does not exist yet.

Resources

• Resources: Read and learn. 24 pages on Stackap about resources, with the details of how each part works today.
• Deploy an app built with Claude Code: Take an app Claude Code built to a live HTTPS address: the pre-flight checks, the agent prompt, what to review and a repo note that keeps deploys repeatable.
• 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: Plain-English definitions of the terms used across Stackap: control plane, project, organization, health check, rollback, PostgREST, R2 and more.
• Move a Next.js app off Vercel: What changes when a Next.js app leaves Vercel for Stackap, feature by feature: crons, variables, images, previews, caching and the domain move.
• Reconstructing a Supabase database: Engineering case study: rebuilding a production Supabase catalog (277 tables, 190 functions, 261 triggers, 220 policies) on PostgreSQL 16, with parity proofs.
• What agent-native means: Agent-native software is built for an agent to operate, not for a person to click through. What that requires, and how it differs from adding AI.

Company

• Company: The people and the principles. 7 pages on Stackap about company, with the details of how each part works today.
• About: Why Stackap exists: building software got easy, operating it and the business around it did not, so one founder built a platform agents can operate.
• 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: 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: 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: 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: 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: The security controls built into Stackap today, how the walls between organizations are tested, and how regulated workloads are handled in early access.

Last updated 2026-10-04.