Resources

Resources

Reading that explains how Stackap works and why, drawn from the pages in the other sections.

Reading that explains how Stackap works and why, drawn from the pages in the other sections.

Every page below states its limits. New guides are added here as they are written.

Pages in this section

• 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 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.
• 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 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 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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 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.
• 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.
• 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.

Last updated 2026-10-03.