One home for every app you vibe-code.
You build them with Claude Code, Cursor or Codex. Sideyard runs all of them on one cheap server you own, each with its own URL, HTTPS, database, backups, jobs and email. The one rule: build on Go + React + SQLite, so every app comes out as a single file.
Building got fast. Hosting didn't.
You can vibe-code an app in an afternoon now. Then it needs a home, and every app means picking a host, a managed database, a cache, a cron service, an email provider and a file store, each with its own account, setup and bill. So most vibe-coded apps never leave localhost, or quietly die on a free tier.
Sideyard is the one place they all live. Each app you push lands on the same server as the others, gets its own URL with HTTPS, and finds its database, jobs, email, sign-in, file storage and backups already there. There's nothing else to sign up for.
Your agent writes the code. Let it use one stack.
Left alone, agents reach for a different stack every time: Next.js here, Postgres there, a queue somewhere else, and each needs its own hosting. On Sideyard every app uses the same four pieces. Your agent doesn't mind, and each app comes out as one small file, so one server holds plenty of them.
No Docker. No Postgres. No Redis. No Node at runtime.
The same app on every popular stacks.
One small notes app, written the way a coding agent writes it on each stack, under the same rising load on one Linux server.
Each simulated user sends one request a second: 80% read the notes, 20% add one. Memory and CPU count the app and its database server together.
Show every number as a table
Loading the measurements…
Pay for one server, not for every app.
The cheapest always-on plans for an app with a database, from each provider's pricing page. Sideyard runs them all on one 4 GB server.
Show how each price is made up
And the free tiers? They're built for one project, not ten.
Prices and limits from DigitalOcean, Heroku, Render, Fly.io, Vercel, Supabase, Railway, Netlify and MongoDB, checked on 22 October 2026, in USD before tax. Sideyard apps that store files or send email also need an S3 bucket and an email provider, shared by every app.
Small, boring and yours.
A bad deploy can't take you down.
A new release gets traffic only after it answers /healthz. If it fails, the old one keeps serving.
Your agent knows the rules.
Every app carries its contract in AGENTS.md, so Claude Code, Cursor or Codex builds features
that deploy on the first push instead of reaching for services your server can't run.
Your server. Your data.
Databases are files you can see, backups land in your own bucket, and apps are plain Go programs. No lock-in.
Everything your apps need. Already built.
One dashboard for every app you've built, and one binary for the whole platform.
Push to deploy
A GitHub Action builds one binary and uploads it. Traffic moves only after the health check passes.
Instant rollback
The last five releases stay on disk. Rolling back starts an older one, with no downtime.
HTTPS domains
A subdomain for every app, plus custom domains. Certificates are issued and renewed for you.
Isolated apps
Each app runs as its own user with memory and CPU limits, and can write only its own folder.
Table and SQL editor
Browse and edit rows, change structure, run SQL, download a snapshot or import a database.
Backups
Every database is snapshotted to your S3 bucket on a schedule. Restore one from the dashboard.
Cron jobs
Schedules, retries and run history. A job is just an HTTP endpoint in your app.
Send through any SMTP provider with one API call. Every app gets a sender and a delivery log.
Sign in with Google
Set up Google and GitHub sign-in once. Every app can use it, and sees who signed in.
File storage
Connect a bucket per app and browse its files. Credentials reach the app as variables.
Encrypted variables
Config and secrets are sealed at rest and never shown again once saved.
Logs and monitoring
Searchable logs, CPU and memory per app, server health, and a flag in the dashboard when an app goes down.
One-click updates
Installs with one command. Updates install from the dashboard and roll back if they fail to start.
Paste one into your coding agent.
Each prompt carries the full Sideyard contract and the starter's code, so it works in any agent with nothing to download. Paste it as your first message and the app comes out ready to host.
Starting something new
Open your agent in an empty folder, paste this first, and write what you want to build in its last section. The agent:
- Creates the starter: Go server, SQLite migrations, jobs, email, Google and GitHub sign-in, React frontend and deploy workflow.
- Saves the contract as
AGENTS.md, so every later session keeps to it. - Checks that it builds and answers
/healthz. - Builds your app inside the stack, then tells you how to deploy it.
Loading…
Moving an app you have
Paste this in your current project. Nothing changes until you approve a plan, and your running app and its database are never touched. The agent:
- Audits the app and writes
SIDEYARD_MIGRATION.md: every service mapped to its Sideyard equivalent, every route, every table. Then it waits for you. - Ports the backend to Go route by route, keeping the API's shape, and the schema to SQLite.
- Copies your data with a re-runnable exporter and checks row counts and integrity.
- Writes the cutover steps, with a rollback that's just pointing DNS back.
Loading…
What you give up, honestly.
Sideyard is for the many small apps you build, not the one that needs a cluster. These limits are choices, and they're what keep it light.
Out of scope, permanently
- Other databases. No Postgres, MySQL or Redis. SQLite handles more than most apps need.
- Other runtimes. No Node, Python or Ruby servers, and no Docker.
- Scale-out. No Kubernetes, autoscaling or GPUs. One server, sized by you.
Limits to know today
- Backups are snapshots. Every 6 hours by default, so a dead server can lose up to one interval.
- Migrations don't roll back. Each one must work with the previous release's code.
- One admin. A single password-protected user, and alerts show only in the dashboard for now.
You won't need any of these.
One server for every app you vibe-code.
One command on a fresh server.
Point *.example.com at an Ubuntu or Debian server, then run:
curl -fsSL https://github.com/rabeeh-ta/sideyard/releases/latest/download/install.sh | sudo bash
It asks for your domain (or offers a free sslip.io name) and an admin password, starts Sideyard as a systemd service and prints the dashboard's address. New versions install from the dashboard with one click, or automatically.