What's included in each plan?

All plans include the complete FastSvelte codebase with source code, documentation, and a single project license. Higher tiers add commercial licenses for multiple projects, priority support, and exclusive Discord access. Check our pricing page for full details.

How quickly can I get FastSvelte running?

After setting up your environment variables (Stripe keys, database URL, etc.), FastSvelte can be up and running in under 5 minutes with Docker. Simply clone the repo, configure your .env file, run docker compose up, and you'll have a complete SaaS application running locally.

Why choose Python backend over Node.js alternatives?

Python's FastAPI backend gives you access to the entire AI/ML ecosystem (OpenAI, LangChain, pandas, NumPy), superior performance, and clean architecture patterns. Perfect for data-heavy applications, AI features, and complex business logic that other starter kits can't handle.

My app isn't Svelte or FastAPI. Can I still use FastSvelte?

Yes. You don't rebuild FastSvelte around your app; you move your app onto FastSvelte. Auth, billing, and teams are already done, so your AI agent only ports your own features, one at a time, into a codebase with clear conventions and typed contracts that keep it from guessing. We migrated a production app this way ourselves; the migration guide at https://docs.fastsvelte.dev/guides/migrating-an-existing-project/ has the step-by-step process and the exact prompts. Prefer React? FastReact at https://fastreact.dev is the same foundation with a React frontend.

Can I deploy FastSvelte anywhere I want?

Yes! Unlike Next.js starters tied to Vercel or Supabase, FastSvelte uses Docker containerization and works with any PostgreSQL database. Deploy to AWS, GCP, Azure, DigitalOcean, or your own VPS. No vendor lock-in means true freedom.

Are there any other costs after purchase?

No hidden costs! You own the code forever. You'll only pay for your own infrastructure (hosting, database) and any third-party services you choose (Stripe for payments, email service, etc.). FastSvelte itself has no recurring fees or licensing costs after purchase.

What kind of support do I get?

All plans include comprehensive documentation and community support. Developer and Team plans include 30 days of email support for technical questions (setup, deployment, integration issues). Team plan includes priority handling for faster response times.

What is your refund policy?

FastSvelte is a digital source code product. Once you receive access to the code, it cannot be returned, so we do not offer refunds. Please review the documentation and demo carefully before purchasing to ensure it meets your needs.

How do team members access the code on a Team license?

Only the license purchaser gets direct access to the FastSvelte source repository. Team members collaborate from the purchaser's private repo. See "Setting Up for Your Team" in the docs at https://docs.fastsvelte.dev/getting-started/#setting-up-for-your-team

Can I upgrade my plan later?

Yes! You can upgrade anytime with 90% credit from your previous purchase. For example, if you bought Solo for $129 and want to upgrade to Developer ($199), you'll only pay $83 more. This makes it risk-free to start with a smaller plan and upgrade as your needs grow.

How to Deploy a FastAPI + SvelteKit App: Your Options

Name: FastSvelte
Author: FastSvelte

A FastAPI backend with a SvelteKit single-page app (SPA) isn’t one thing to deploy. It’s three, and that works in your favor: each piece can go wherever suits it best, and you can move one without touching the others.

This post covers where each piece can live and the common ways to combine them. Each setup links to a full step-by-step guide. If you’re still deciding on the architecture itself, start with SvelteKit vs FastAPI.

1. What you’re deploying

Piece	What it is	Address
API	FastAPI container	`api.example.com`
App	Static SPA files	`app.example.com`
Database	PostgreSQL	Private

A marketing site, if you have one, is a fourth piece: more static files, usually at example.com.

Keep the app and the API under the same domain, as in the table. That’s what lets the browser send your session cookie to the API.

2. The frontend

This is the easy part. npm run build gives you a folder of static files, and almost anything can serve them:

Vercel
Cloudflare Pages
Netlify
Azure Static Web Apps
AWS S3 with CloudFront
DigitalOcean
Plain Nginx on your own server

Many of these have a free tier, and switching later mostly means uploading the same folder somewhere else.

3. The API

This is the only piece that needs a running server, so it’s where your choice matters most.

Most FastAPI apps run in a container, and you have plenty of places to host it:

Railway
DigitalOcean
Fly.io
Azure Container Apps
Your own VPS
FastAPI Cloud (in beta), from the team behind FastAPI

Anything that runs Docker can run the same image, which makes moving between hosts straightforward. We’d skip function-style serverless like AWS Lambda for a full API, because a container is simpler to run and gives you the same app everywhere.

4. The database

Use managed Postgres unless you have a good reason not to. Backups and updates become someone else’s job, which is a bad thing to get wrong by yourself.

Any Postgres will work, so you have plenty of choices:

Neon
Supabase
Railway
DigitalOcean Managed Databases
Azure Database for PostgreSQL
AWS RDS
Your own VPS, if you’re happy to handle backups yourself

Wherever it lives, keep it in the same region as your API, because nearly every API request talks to the database.

5. Common setups

Each of these reaches the same result. Pick the one that matches how much you want to manage.

Railway puts everything in one place. It’s the simplest of the five and the quickest way to get live.
DigitalOcean App Platform runs the container and static sites next to managed Postgres, all with one provider.
Fly.io + Neon + Vercel picks a specialist for each piece. You get three dashboards instead of one.
Azure uses Container Apps, PostgreSQL Flexible Server and Static Web Apps. It makes most sense if your company is already on Azure.
Docker Compose on a VPS runs everything on one server. You get full control, and TLS, backups and updates become your job.

6. What every setup needs

Whichever you pick, the same list applies:

Environment variables for the API, like the database URL and secrets.
The API’s address set before you build the frontend, because it ends up inside the static files.
Migrations run against the production database as their own step, before the new code goes live.
HTTPS. Most platforms handle it, and on a VPS your reverse proxy does.
CORS on the API, allowing your app’s exact address with credentials turned on.

Our production guide covers the config, cookies and CORS in detail.

7. How to choose

If you want to be live today, use Railway. If your company already runs on a cloud, stay there. If you want control and don’t mind the upkeep, take a VPS. For a side project, try FastAPI Cloud’s free plan with a static host and a free Postgres tier, knowing that free apps sleep when idle.

The choice isn’t permanent. The API is a container, the frontend is static files and the database is plain Postgres, so you can move one piece at a time as your needs change.

FastSvelte is a SvelteKit SaaS boilerplate built this way, with a Dockerfile for the API and a guide for each of the five setups above.