Cynchro Cloud — PaaS

Self-hosted platform-as-a-service (like Render / Fly.io / Vercel) running on your own VPS. You push a Docker image or a Git repo and get a container running behind an HTTPS domain with an automatic Let’s Encrypt certificate — no manual server work.

POST /deploy  →  build/pull image  →  run container  →  https://<app>.cynchro.cloud

Two ways to use it

	Where	Best for
Dashboard	`https://app.cynchro.cloud`	clicking through deploys, logs, secrets
REST API	`https://api.cynchro.cloud`	automation, CI, scripts

Replace cynchro.cloud with your own ROOT_DOMAIN if you run a different instance. Every app gets https://<name>.<ROOT_DOMAIN> unless you set a custom domain.

Start here

Getting Started — log in and deploy your first app in 2 minutes.
Deploy a Docker Image — the simplest path (any public image).
Deploy from Git — build from a repo + push-to-deploy webhooks.
Multi-Service Apps — run several containers as one app (web + db, etc.).
Secrets — inject config/credentials safely (env vars or files).
Managing Apps — logs, restart, stop, delete, limits & quotas.
API Reference — every endpoint and field.
Troubleshooting — what each error means and how to fix it.

Core concepts

Org (tenant) — your account owns an org. Every app/secret is scoped to it; you never see other tenants’ resources.
App — one deployable unit, identified by a DNS-safe name, unique within your org. Redeploying the same name updates it in place (idempotent).
Service — a single container. A normal app has one; a multi-service app has several (exactly one is public).
Deployment — one build/run attempt for an app; has logs and a status.
Secret — a named, encrypted bag of key/values you reference from apps.

How it works (30-second tour)

You call POST /deploy (or use the dashboard form).
The control-plane API validates, encrypts any secrets, and queues a job.
A worker pulls or builds the image and starts the container with CPU/memory limits and security hardening.
Traefik (the edge router) issues a Let’s Encrypt cert and routes https://<your-domain> to the container.

You only ever talk to the API/dashboard — the rest is automatic.