Introducing Sticklight Cloud
Deploy from GitHub. Live in minutes.
Connect your repo and deploy to Sticklight Cloud in minutes - without configuring infrastructure or managing DevOps.
01 · The workflow
Build with AI. Host with Sticklight.
Sticklight Cloud lives at the end of your AI-native workflow. Code in Cursor or Claude Code, push to GitHub, and we take it from there. No context switch, no separate account, no glue code.
Build
·
Push

Ship

02 · How it works
Four steps to a live URL.
01
Connect GitHub
Pick a repo and a production branch. Public or private, both work. We handle the auth handshake.
02
Detect the stack
Framework, install command, build command, output folder. Confirmed or edited by you.
03
Build & deploy
Isolated build. Artifacts pushed to our global edge network. Usually under 60 seconds.
04
Manage in one place
Live URL, deployment logs, env vars, rollback, redeploy. Nothing hidden.
03 · What ships today
Production-minded from day one.
Not toy hosting. Every deploy comes with the plumbing you would expect from a serious platform.
Exclusive
Private repos, from day one
Deploy from private GitHub repos with the same one-click connect. No workarounds, no forks.
Exclusive
Teams built in
Every deploy plugs into Sticklight Workspaces. Roles, invites, and per-project access, no separate ACL tool.
Exclusive
Global auto-CDN
Every deploy routes to the data center closest to your visitor. Fast first paint, everywhere, no config.
Framework detection
React, Vite, Vue, Astro, and more. We read the repo, you confirm or edit.
Coming soon
Environment variables
Per-project secrets, injected at build and runtime. Encrypted at rest.
Deployment logs
Full build output, streamed live. Every deploy, every artifact, kept for review.
Instant rollback
Every deployment is versioned. One click to revert. No rebuild required.
Deploy on push
Every push to your production branch triggers a new deployment. Or hold and promote manually.
Coming soon
Custom domains
Bring your own domain with automatic SSL. Landing shortly, part of phase two.
04 · Vote on phase two
Phase two is being written right now.
We are building Sticklight Cloud with you, not in a vacuum. Pick what matters most, then send us your votes—we will reach out the moment it ships.
Deploy from Claude Code & Cursor
Trigger deploys directly from your AI coding session via the Sticklight MCP. No terminal, no tab-switch.
Preview deploys per PR
Every pull request gets its own URL. Review the change, not just the diff.
CLI + SDK
npx sticklight deploy. Ship from your terminal, your CI, or your script.
Staging & production environments
Promote from staging to production without a rebuild. Stable URLs per environment.
SSR & API routes
Server-side rendering and lightweight API endpoints, not just static.
Analytics dashboard
Requests, cache hits, error rates. Read the health of every deploy at a glance.
Deploy notifications
Slack, Discord, and webhooks. Get pinged when a deploy ships, fails, or gets rolled back.
Password-protected preview URLs
Share previews with clients and stakeholders without exposing them to the whole internet.
05 · FAQ
FAQs
No. Cloud Backend is the database, auth, and storage layer that AI-built apps use inside Sticklight Studio. Sticklight Cloud is where you host code from GitHub. Two different tools that share a brand.
Studio publish is for the vibe-coded path, one click from Sticklight to a live URL. Sticklight Cloud is for code you write yourself—or with Cursor or Claude Code—and push to GitHub. Same company, different entry point.
Not yet. Phase one is static sites. SSR and API routes are on the roadmap. If you want them, vote for them above.
Today, push to GitHub and we deploy automatically. Direct MCP-based deploy from Claude Code and Cursor is on the phase-two roadmap; vote for it to push it up the queue.
Free right now, limited to five projects including anything you have live on Sticklight Studio. Pricing beyond that lands with phase two, with a real free tier and no usage-cliff surprises.
Ready to deploy?
Import a repo, watch it go live, then help us shape what comes next.