Introducing Sticklight Hosting: Whatever you build. Wherever you built it.

You’ve built your workflow. Cursor for the flow, Claude Code for the heavier lifts, GitHub as the source of truth. Then comes publish day and the whole thing seizes up. A different stack, a different pipeline, a config file that eats your afternoon.

Sticklight Hosting is our answer to that. Git-based hosting for the code you write in the tools you already use. Push to GitHub, and we take the publish off your plate. The build, the global edge, the logs, the rollbacks. Your habits stay. Your site goes live.

Not the same as Cloud Backend

Cloud Backend is the in-Studio layer for databases, auth, and storage that powers the apps you build with the AI. If you’ve spun up a web app that stores data or logs users in, that’s Cloud Backend at work. It stays.

Sticklight Hosting is the new one. Hosting for the code you write in your own editor, wired to your GitHub provider, and served from a global edge from the first deploy.

Same family. Different jobs.

Push from wherever you code

The workflow doesn’t move. Cursor, Claude Code, your own editor, or Sticklight Studio. Whatever tool gets you into flow is the tool you keep. GitHub is the handoff. From there, Sticklight Hosting takes over.

That’s the whole idea. Sticklight Cloud is a hosting layer, not another editor. Nothing to rewrite, nothing to relearn.

The build handles itself

The moment a push lands, Sticklight reads the repo, detects the framework, and runs the build. No YAML to hand-craft. Framework detection covers the static and static-first stack you’re likely already on: Next.js (static export), Astro, Vite, SvelteKit (static), plain HTML. If it builds to static assets, we know what to do with it.

Deployment logs stream while the build runs and stay on the deployment for as long as you need them. Environment variables edit without opening a terminal. Every deploy is kept, so rollback is one click to any previous version, and production points at the old build instantly. Nothing rebuilds.

A build breaks, you’re back to the last good one before the panic sets in.

The publish handles itself

Every deploy serves from a global auto-CDN. No region to pick, no configuration file, no add-on plan. Your visitors are close to your site wherever they are, from the first push.

Private repositories work on day one, so proprietary code and client work live in the same pipeline as everything else. Teams work on day one too. Bring your teammates into the same workspace and everyone deploys, rolls back, and reads logs in the same place. Custom domains sit on the Pro plan. Bring your own domain, add the DNS record we hand you, and you’re live under your own name with HTTPS handled.

The roadmap doesn’t

The rest of what we want to build is drafted, not decided. Preview deploys per pull request. A CLI and SDK. Staging and production as first-class environments. SSR and API routes. An analytics dashboard. More.

What we haven’t decided is the order.

On the launch page, every roadmap item is a vote. Tap the ones you’d use tomorrow and we ship in the order the vote tells us to. The teams who live in preview deploys see theirs climb. The teams who need SSR to move over see that one climb. We build accordingly.

Try it

Open the launch page, connect a repo, and watch a first deploy go from a commit to a live URL. Then tell us what phase two should be.

FAQ

Do I need to switch editors to use Sticklight Cloud?

No. Sticklight Cloud is a hosting layer, not an editor. Code with Cursor, Claude Code, your own IDE, or Sticklight Studio. If it lands on GitHub, Sticklight Cloud can ship it.

Is this the same as Cloud Backend?

No. Cloud Backend is the database, auth, and storage layer inside Studio, used by apps built with the AI. Sticklight Cloud is Git-based hosting for your own code. Different products, same family.

What frameworks are supported?

Static and static-first frameworks, including Next.js (static export), Astro, Vite, SvelteKit (static), and plain HTML. If it builds to static assets, Sticklight Cloud runs it. SSR and API routes are on the phase two list.

Do private repos and teams cost extra?

No. Both are available on day one, no upgrade required. Custom domains sit on the Pro plan.

What happens to a bad deploy?

Every previous deploy stays available. Roll back in one click and production points at the old version instantly. Nothing rebuilds.

When does phase two ship?

The order is set by the vote on the launch page, so timing depends on where the interest lands. We’ll ship items as they finish, rather than as one bundled release.