Orcaru / Sites
Launch a site
Managed sites · GitHub → Cloudflare edge

Launch client sites in minutes, not sprints.

Give Orcaru a name. It stands up the whole site — repo, a live and a staging URL, automatic SSL, verified deploys — on Cloudflare's edge. Point any domain without touching DNS. Manage all of it just by chatting.

Live + staging, every site SSL on any domain Roll back in one move
The tax on every launch

A new site shouldn't cost you a sprint.

Every client launch drags in the same overhead — a repo to spin up, DNS to wire, an SSL cert to chase, a host to pick, staging to stand up, and the quiet dread of promoting to production without breaking what's live. It's the work between you and the launch. It's not the work you're good at.

External
The infrastructure detour
GitHub, DNS, TLS, hosting, environments — five tools and a runbook before a single pixel ships.
Internal
You've become the ops team
Babysitting certificates and deploy steps instead of doing the creative work the client hired you for.
The stakes
One wrong promote
Hand-rolled hosting means a bad deploy takes production down — on the client's domain, in front of their customers.
Meet your guide

We wired the hard parts together, so you don't have to.

You're here to launch great sites for clients — not to memorize the Cloudflare dashboard. Orcaru keeps GitHub as the source of truth and Cloudflare Pages as the edge, and threads DNS, SSL, staging, and promotion through one clean path. Every deploy is checked against the exact commit it claims to be.

2
URLs per site — live and staging, from day one
0
DNS migrations — SSL issues on the client's own domain
1
move to promote staging → production, or roll it back
100%
of deploys verified against their commit before they count
The plan

Three steps to a live site.

No runbook, no handoff to engineering. The same three steps whether you click through the dashboard or say it in a sentence.

Name it

Tell Orcaru the site. It derives the slug, spins up a GitHub repo from your template, and reserves the domains.

"Add a site for Born From Water."

Orcaru provisions it

A repo, a Cloudflare Pages project, a live and a staging URL, and SSL — all stood up and verified. Nothing for you to wire.

repo → pages → live + staging → ✓ verified

Point a domain, go live

Add the client's domain with a single CNAME — SSL issues itself. Promote staging → production the moment it's ready.

"Point new.bornfromwater.com at the live site."
What every site comes with

Built like a platform. Runs like a reflex.

// environments

Live & staging, always

Every site ships with both URLs. Preview on staging, then promote the exact commit to production.

// tls

SSL on any domain

Your client keeps their DNS wherever it is. A CNAME is all it takes; Cloudflare issues and renews the cert.

// safety

Promote & roll back

Reviewed promotion to production, and a one-move emergency rollback that reconciles Git back to what's live.

// proof

Verified deploys

A status isn't "green" until the live URL returns the commit it should. No guessing what's actually out there.

// scale

Many sites, one workspace

Run every client's site — and its variants — under one project, each with its own repo, domains, and history.

// source of truth

Git underneath it all

Every change is a commit. GitHub stays the source of truth; Cloudflare just serves what Git says.

The Orcaru difference

Manage every site in plain language.

Spin up a staging site, point a client's domain, check what's live, roll production back — say it, and Orcaru turns the sentence into a verified deploy. The same actions as the dashboard, from wherever you already work.

Your clients can drive their own sites the same way — no dashboard tour, no Cloudflare login, no ticket to you.

The choice

Keep hand-rolling, or start shipping.

Without Orcaru
  • A half-day of setup before the first client review
  • SSL and DNS tickets bouncing between you and the client
  • Deploys you can't fully trust are actually live
  • A bad promote that takes production down
With Orcaru Sites
  • A live and a staging URL in minutes, from a name
  • SSL that issues itself on the client's own domain
  • Every deploy verified against its commit
  • Safe promotion, and a rollback that can't diverge from Git

Every client site — live, staged, secured, and yours to manage in a sentence.

Your next launch

Make waves with your next site.

Name it, and watch the repo, the URLs, and the SSL take care of themselves. Your first site is a sentence away.

github source-of-truth · cloudflare edge · verified deploys