Deployment service

Stuck at deploy? Fixed price, fixed scope, done in writing.

You downloaded a SvelteKit SaaS starter. It runs locally. It does not run on your infrastructure, and the docs will not tell you which of six failure modes you have hit.

I will get it running in your own accounts, for a fixed price agreed before I start, and hand you a written record of exactly what I did.

$149 · $299 · $499 — see what each covers below.

See the prices ·see what this does not do

The free kits are not being maintained. That is checkable.

Last commit to each project:

VerdantStack        2026-10-02   ← three weeks ago
CMSaasStarter       2026-03-21   ← six months
justship            2024-11-22   ← twenty-two months
KitForStartups      2024-06-08   ← twenty-eight months

KitForStartups’ README still points you at checking the age of dependencies such asLucia — a library its own author has since deprecated. Its authentication dependency died and nothing replaced it.

The three largest free SvelteKit SaaS starters sell nothing: CMSaasStarter’s pricing page is a demo of its own Stripe integration (“Still actually free!”, with a test card number), KitForStartups has no pricing at all, and justship’s website is a dead 404.

So the field is not crowded with maintained alternatives. It is empty of them. A free clone can match a feature list. It cannot match someone fixing it.

You can probably do it yourself. Here is the honest case for paying anyway.

Do it yourself if: your target platform is Cloudflare Pages with a Postgres transaction pooler on :6543; you already know that your connection-string password must be URL-encoded; and you know thatwrangler pages secret put writes to the productionenvironment only, so your preview branch silently gets Missing DATABASE_URL.

If you already know all three of those, this service is not for you.

Pay for it if: any one of those is news, or you have a deadline, or you have read the same deployment paragraph three times and it still has not worked.

What you are buying is not knowledge. All of the above is in free documentation and in the starter’s own README. You are buying the four hours where something goes wrong that the docs do not mention.

Three prices. You know which one you need before you ask.

T1

Reference deploy

$149

Cloudflare Pages + Postgres (or D1). The path we run ourselves.

  • • Your database provisioned and migrated
  • • Your app deployed and building
  • • Health endpoint verified over your own domain
  • • Login and role-based access checked
  • • A written runbook of everything deployed, how to redeploy, and how to roll back

T2

Alternate platform

$299

Everything in T1, on a platform we do not already run in production.

  • • Vercel, Railway, Fly.io, Netlify, or Docker-only hosting
  • • Everything in T1, on your platform
  • • The extra cost is not the deploy — it is that we do not already know your platform’s sharp edges

T3

Deploy and harden

$499

Everything in T2, plus the things that go wrong after the first deploy.

  • • TLS configured
  • • Connection pooling sized and documented
  • • Optional Postgres row-level-security policies applied
  • • A written backup and restore procedure
  • • A CI pipeline running the starter’s own test suite

All three: you hold every account. We never create, own, or hold one. Your infrastructure stays yours, and it stays yours after we leave.

What this service does not do.

  • It does not develop your application. No features, no UI, no business logic, no schema changes beyond the starter’s own migrations.
  • It does not buy anything for you. No managed database plan, no domain, no email service, no paid tier from a third party. Your bills stay your bills.
  • It does not touch your existing production data. Migrating what you already run is your operation, on your plan, with your backups.
  • It does not run your app for you. No monitoring, no on-call, no uptime guarantee, no incident response. When the engagement ends, it is yours to operate.
  • It does not do security testing or certify anything. Hardening a deployment is not making your product secure or compliant.
  • It does not train your team. There are no calls and no workshops — this is written work and written answers only.
  • It does not support the code you change. Your licence already covers questions about the starter itself; once you start modifying it, that is outside scope — and it says so in the licence, not just here.

Four steps. Written throughout.

  1. 1. You tell me the platform and the plan. Written only, no call.
  2. 2. I quote a fixed price for the written scope. Before anything starts.
  3. 3. You give me access to accounts you own. Migrate, deploy, verify — I pause and confirm at three points: environment reachable, migrations applied, before the production domain switches.
  4. 4. You get a runbook and a 5-day acceptance window. If any of the deliverables are not met in those 5 days, I fix them at no charge. After that, the deployment is yours to operate.

Support for 14 days after acceptance, in writing, 48-hour target. No calls, ever.

You will not get a name, a face, or a call. Here is why that is the safe version.

You will not be dealing with an anonymous person. You will be dealing with a published scope, a fixed price, a written runbook you keep, and a licence whose terms are public before you pay. Every one of those is checkable without ever speaking to anyone.

What you are not getting: an employment relationship, an agency, an on-call commitment, or access to a person. The counterparty is a brand with a public track record of dated releases and a public licence.

Start with the scope, not the call.

Tell me the platform and the plan and I will reply with a fixed price for a written scope. Async only, 48-hour target. If it is not a fit, I will say so and say why.

Write to us ·read the licence first ·the starter kits themselves

This page states no client count, because there is none. The service is new and unproven; everything above it is a published scope and a fixed price, not a track record.