Skip to content
Sunloft Pro

Nobody should file a ticket to change a headline.

Your team edits your real coded site on drafts. Every draft is checked, approved by the right person and published in one click.

Early access. 14-day trial with 50 edits when you connect, no card.

acme.com/pricingDraft: Pricing update
Demo site, illustrative

The ticket queue, gone.

Changing a headline on a coded site usually takes three people and a sprint. On Pro it takes the person who wrote it and the person who approves it.

Before Sunloft

  1. File a ticket.
  2. Wait for the next sprint.
  3. A developer makes the change.
  4. Someone reviews the pull request.
  5. It goes out with the next deploy.

With Sunloft

  1. Ask for the change.
  2. The right person approves it.
  3. Publish.
Editing

Drafts, not branches.

Everyone on the team edits the real site in the same editor as Start. Each piece of work is a draft with a plain name, so nobody learns git to change the pricing page.

acme.com/pricingDraft: Spring pricing pageShare

Drafts

Spring pricing pagePriya, 2 hours agoLayoutWaiting for Sam
New careers pageDan, yesterdayNew pageIn progress
Fix the footer linksPriya, MondayCopyPublished
New draft

Spring pricing page

  • Changed/pricing, /plans/growth
  • 9 checks passed
  • SWaiting for Sam to approve
AcmeProductCustomersPricingDocsStart a trial

Simple pricing for finance teams

Every plan includes unlimited users and a 14-day trial.

Starter$29One entityWeekly bank syncEmail supportStart a trial
Growth$89Up to 15 entitiesDaily bank syncApproval flowsStart a trial
Scale$199Unlimited entitiesHourly bank syncSSO and audit logTalk to us
Demo site, illustrative
Checks

Checks a good developer would run.

Every draft runs them before anyone is asked to approve it. Seven block publishing and two warn. Only a developer can override a block, and they have to say why.

CheckWhat it catchesIf it fails
buildThe site doesn’t build, or a page fails to renderblocks
indexabilityA stray noindex would hide this page from Googleblocks
linksLinks to pages that don’t exist any moreblocks
page-titlesMissing, duplicated or overlong titles and descriptionswarns
redirectsLoops, chains, and a renamed page with no redirectblocks
accessibilityMissing alt text, low contrast, unlabelled buttonsblocks
speedA page that got slower than the budget your developer setwarns
guardrailsA change to a file your developer locked, like config or packagesblocks
content-safetyText or links that look like spam or phishingblocks
Review

Approvers look at pictures, not code.

Every draft has a before and after of each page it touched, at desktop and phone width. Drag either one and both move.

Before
Before
Demo site, illustrative

Approval rules a marketer can pass.

Written once, in sentences, separate from GitHub. Anyone you send a share link to can look and leave comments pinned to the page, with no account and no seat.

acme.comRules

Copy and blog posts: editors publish.

Layout and new pages: one approver from Priya, Sam.

Shared components, styles and redirects: a developer.

Config, packages and CI: never touched.

AcmeSpring pricing page
AcmeMenu

Simple pricing for finance teams

Growth$89Up to 15 entitiesStart a trial
Starter$29One entity
JJo Can we say “entities” in plain words? Most people won’t know it.
MMark Approved from legal.
Demo site, illustrative
For developers

For your developer.

Locked paths and check settings live in sunloft.json in your repo, read from main, so your developer owns them and a draft can’t change them.

sunloft.json
{
  "version": 1,
  "framework": "next-static",
  "root": "apps/web",
  "protected": [
    "src/lib/**",
    "next.config.ts",
    ".github/**"
  ],
  "checks": {
    "a11y": "serious",
    "links": "internal",
    "budgets": { "pageKb": 1500, "lcpMs": 2500 }
  }
}

Read from main, never from a draft.

The agent can’t write sunloft.json, and a draft can’t loosen it.

A sandbox with no secrets.

Each draft runs alone, with no production secrets and a network limited to your package registry.

A token for one repo.

Scoped to your site’s repo, and it expires with the draft.

A developer view.

The branch, the diff and the logs, for the people who want them.

Only developers override a blocking check.

And they have to give a reason, which is logged.

Host with us, or keep your host.

Static sites can live on Sunloft. Anything else stays where it is: publishing merges to main and your host builds it as it always has. Either way, rolling back is one click.

Host with us

Publish puts the approved draft live on your domain. Every publish is a version you can go back to.

Publish 3 changes

9 checks passed

Publishes to acme.com

Publish
  • Version 41 Fix the footer linksRoll back to this

Keep your host

Vercel, Netlify, Cloudflare Pages, or anything that reports to GitHub. A rollback lands as a new commit.

Spring pricing page

  • Approved by Sam
  • Merged into your main branch
  • Building on Vercel

Status read back from your GitHub deployments.

Price the site, not the seat.

Pro is $99 a month per site, with unlimited editors and free commenters. Approvals are included, not an Enterprise extra.

Agencies run five sites on Team for $399 a month, each client in their own workspace with one shared allowance of edits.

See plans

Lantern StudioNew client
  • NNorthfield Dental1 site1 approval waiting
  • HHarbour Coffee Roasters2 sites
  • KKestrel Physio1 site2 drafts in progress
  • TTidewater Records1 site
Demo site, illustrative

What your team will ask.

Is Pro open now?

Pro is built and in early access. Sign in and connect your repo. If connecting isn’t open for your account yet, the connect page says so and gives you an address to write to, and you can make a Start site in the meantime.

How do we connect?

Sign in with your email, install the Sunloft app on GitHub for your site’s repository, and Sunloft checks the site builds before anyone edits. The 14-day trial starts then, with 50 edits and no card.

Which frameworks does Pro work with?

Setup recognises Astro, Next.js, Vite, Eleventy, Hugo and plain HTML, including a site in one folder of a monorepo. Hosting with us needs static output, such as a Next.js static export; a server-rendered site keeps its own host. For anything else, setup says plainly when you connect whether it can build and preview it.

Is our code used to train AI?

No. Your repo and your drafts are never used to train models, ours or anyone else’s.

What about branch protection?

It’s respected. Publishing merges an approved draft into main through Sunloft’s GitHub App. If main needs a GitHub review, setup says so and shows your developer the two ways to allow it.

What about our secrets?

Drafts run in a sandbox with none of your production secrets, a network limited to your package registry, and a GitHub token for that one repo that expires with the draft.

We host on Vercel. Do we have to move?

No. Keep your host: publish merges to main, your host builds it as usual, and Sunloft reads the deployment status back from GitHub so the editor shows “Building on Vercel”, then “Live”.

Isn’t this what Webflow Source does?

Webflow announced Source on 2 September 2026 as a research preview, with no price or release date when we checked on 18 October 2026. It describes something similar. Sunloft Pro is built, in early access, and has a public price: $99 a month per site.

What if Sunloft goes away?

Your site is in your repo and on your host the whole time. If Sunloft stopped tomorrow, your site would keep running and your developer would carry on as before.

Nobody should file a ticket to change a headline.

Connect your repo and the whole team edits on drafts, with checks and approvals.

Early access. 14-day trial with 50 edits, no card.