Ship a repository.
Point us at a Git repository with a Dockerfile. You get a running container, a URL, and a project of your own.
Continue with GitHubChoose a plan
Free trial
One site on our managed hosting for seven days. No card, nothing to cancel, and the whole pipeline: screening, build, certificate, logs and push-to-deploy.
Or choose a paid plan — Starter, Full, or bringing your own VPS.
Deploy a new project
Point us at a GitHub repository with a
Dockerfile. We screen the code, build it, and give it a
live HTTPS address.
Deploying
Starting…
- Waiting for a free build slot
- Checking the repository
- Checking your domain's DNS
- Screening the code
- Isolating your project
- Creating project and application
- Handing over the project
- Preparing your server
- Building and deploying
- Issuing the TLS certificate
- Stopping the application
- Waiting for the containers to go
- Removing our software from your server
- Leaving your server as it is
- Confirming the address no longer answers
- Terminated
Congratulations — you're live.
Your project has been provisioned and deployed.
Deploy automatically when you push to GitHub
On. Each push to the deployed branch is screened, then that exact commit is built and deployed. Nothing to set up.
Add this webhook to the repository under Settings → Webhooks → Add webhook. Every push to the deployed branch then rebuilds and redeploys on its own.
- Payload URL
- Content type
- application/json
- Secret
Your projects
Start, suspend or terminate what you have deployed.
Nothing deployed yet. Start a .
| Address | Owner | Hosting | State | Actions |
|---|
Deploy automatically when you push to GitHub
On, through the Ordo Kit GitHub App. Each push to the deployed branch is screened first, then that exact commit is built and deployed.
If you added a webhook for this by hand earlier, remove it from the repository’s Settings → Webhooks: it would build every push a second time, without screening.
Recommended: give Ordo Kit access to the repository on GitHub, and every push is screened before it is built. Or add a webhook by hand:
Add this webhook to the repository under Settings → Webhooks → Add webhook. Every push to the deployed branch then rebuilds and redeploys on its own.
- Payload URL
- Content type
- application/json
- Secret
- ••••••••••••
Your own domain
Serve this site at a hostname of yours as well as at its shared address. Point the hostname’s DNS here first; if it is not in place yet, the answer names the exact record to add. Changing it redeploys the site, without a rebuild, and orders a certificate for the new name.
Build timeline
| Time | Source | Step | Detail |
|---|
Actions
| Time | Who | Action | Outcome |
|---|
Billing
Your plan, what it includes, and how you pay for it.
- Sites
- Each site
- Bandwidth
-
Change plan
Payments are in test mode: use the provider's test cards, and nothing is charged.
Danger zone
Terminates every project, cancels a paid plan at once with no refund, and deletes your plan, connected apps, API tokens and keys. It cannot be undone.
Support
A question, a problem, or something that doesn't look right. Write to us here and we'll answer by email.
Support mail is not configured on this instance, so this form has nowhere to send to.
A copy isn't sent to you; keep a note if you need one.
Settings
How agents reach your account. Connect one by signing in, see what is connected, or make a token for a script.
Verify a card to use the MCP API
Connect an agent
Give your agent this address. It sends you here to sign in with GitHub and approve it, and it connects - there is no token to copy. Full tool reference: MCP
- Address
- Sign-in
- GitHub, then approve on our consent page
Add it to your agent
Connected apps
Nothing is connected yet. to see it here.
| App | Connected | Last used | Actions |
|---|
API access
For scripts and CI, where a browser sign-in isn't possible. A token acts as you - same quota, same ownership, same audit trail - and is sent as a header on every request:
Creating tokens opens with MCP access; see above.
Copy this now
This is the only time it can be shown — only a hash is kept, so it cannot be recovered. If you lose it, revoke it and make another.
Your tokens
No tokens yet.
| Name | Created | Last used | Actions |
|---|
Admin
Teams, projects and deployments
Accounts
Every Coolify account, and the team its login lands on.
| Account | Name | Teams | Lands on |
|---|
User timeline
Everything recorded about one account, newest first: plan, audit, activity in the wizard, deployment events, GitHub deliveries and log lines.
Nothing recorded in this window.
Alerts
What you are told about: every alert on Telegram at once, failures by mail at once, and a mail digest of everything every day.
| When | Kind | Account | Project | Details | Telegram |
|---|
No alerts in the last 30 days.
Granted plans
Capacity
Loading…
Waitlist
Nobody is waiting.
| # | Account | Joined | Told a place opened |
|---|
Free trial
Held for phishing review
A site is held when the phishing check finds strong signs: a form asking for a wallet's recovery phrase, a password form under another brand's name that sends what is typed elsewhere, or kit code that captures passwords. It is stopped, and neither its owner nor the bandwidth meter can start it. Release starts it again; Terminate removes it. Weak signs only alert. Every running site is re-checked daily.
Nothing is held.
| Site | Owner | Why | Held | Actions |
|---|
Certificates on the managed server
Tenant sites should all be served the zone's wildcard, kept in
acme-dns.json. A tenant name in acme.json
ordered a certificate of its own over HTTP-01, which spends the
weekly Let's Encrypt limit. The wildcard's expiry is read from the
server's own handshake at PUBLIC_IP, past Cloudflare:
under 20 days left means renewal is failing, under 7 is urgent.
Nothing to report: the wildcard is in place and no tenant name holds a certificate of its own.
Hostname conflicts
More than one application published on the same address. The proxy registers both, and which one answers is not something anyone chose.
Nothing to report: every address is published by one application.