Host Your App on Sticklight Cloud

Host code from GitHub on Sticklight Cloud. Connect your repository, confirm the build settings, and your static site goes live on a Sticklight subdomain with automatic deploys on every push.

Who can do this: Any signed-in user can import and deploy a project. Sticklight Cloud projects count toward your workspace project limit. See Roles and Permissions for details.

How It Works

Build with AI in Cursor, Claude Code, or your editor of choice. Push to GitHub. Sticklight hosts it.

The workflow:

1. Connect your GitHub account
2. Pick a repository and production branch
3. Sticklight detects your framework and suggests build settings
4. Confirm or edit, then deploy
5. Your site is live within about a minute

Every push to your production branch triggers a new deploy automatically. You manage everything from the same workspace as your other Sticklight projects.

When to Use Sticklight Cloud

Use Sticklight Cloud when:

• Your source of truth is a GitHub repository
• You want deploys in the same workspace as your Sticklight Studio projects

Use Sticklight Studio when:

• Building in Sticklight Studio: Use Publish instead. Sticklight Cloud does not import Studio projects.
• You need a database, login, or file storage, and don’t have the technical expertise to set it up yourself: Use Cloud Backend with a Studio project. Sticklight Cloud provides edge delivery only, not backend services.
• Your app requires a server: Next.js, Nuxt, Remix, SvelteKit with SSR, Express, Fastify, and similar frameworks are detected on import and blocked. Sticklight Cloud serves static files only.
• Your repo is a monorepo: Projects with nx.json, turbo.json, pnpm-workspace.yaml, Lerna, Rush, or npm/pnpm workspaces are not supported.
• You need a custom domain now: Custom domains for hosted projects are coming soon. For custom domains today, use Studio Publish.

Supported Frameworks

Sticklight Cloud works with any static or static-first stack:

• React, Vue, Preact, Svelte with Vite, Create React App, or Vue CLI
• Plain Vite or static HTML
• Static generators: Astro (static mode), Gatsby, Docusaurus, VitePress, Eleventy, Hexo, Gridsome

Sticklight reads your repository and suggests the install command, build command, and output folder. You can edit these before deploying.

Importing a Project

1. Click Hosting in the sidebar, or click Import a project from the Hosting page
2. Connect your GitHub account if you have not already
3. Select a repository (public or private)
4. Choose your production branch
5. Review the detected build settings:
   • Framework (detected automatically)
   • Install command (e.g., npm install)
   • Build command (e.g., npm run build)
   • Output folder (e.g., dist)
6. Add environment variables if needed
7. Click Import & deploy to go live, or Import only to set up without deploying

If you reach your project limit, you will see an upgrade prompt. Delete an existing project or upgrade your plan to continue.

Managing Your Deployment

After importing, your project page shows:

• Overview: Live URL, preview screenshot, deploy status
• Deployments: Full history with logs, the option to cancel in-progress deploys, and rollback to any previous successful deploy
• Environment variables: Add, edit, or import from a .env file. Changes apply on the next deploy.
• Settings: Rename, change the production branch, or delete the project

Auto-Deploy

By default, every push to your production branch triggers a new deployment. You can turn this off in project settings and deploy manually when ready.

Rollback

To revert to a previous version:

1. Go to Deployments
2. Find the deployment you want
3. Click Rollback

Rollback starts a new build using that commit and its environment variable snapshot. It is not an instant switch to old files.

Environment Variables

Environment variables are injected at build time. Add them in the project settings before your first deploy, or import a .env file.

Changes to environment variables are not live until the next deploy. If you update a variable, trigger a new deploy to apply it.

Secrets are not yet supported. Do not paste production API keys or sensitive credentials.

Sticklight Cloud vs. Sticklight Studio vs. Export to GitHub

Product	What it does
Sticklight Cloud	Deploy static sites from GitHub to a Sticklight subdomain
Sticklight Studio	One-click publish for projects built in Sticklight Studio
Export to GitHub	Push Studio project code to GitHub for backup (one-way sync)

Same company, different entry points. Use Sticklight Cloud for code that already lives on GitHub. Use Sticklight Studio for projects you build inside Sticklight.

Current Limitations

• Static output only. Server-side rendering and API routes are on the roadmap but not available yet.
• One environment per project. Staging environments are not supported.
• Custom domains coming soon. Hosted projects get a .sticklight.app subdomain. Custom domain support is in development.
• No secrets vault. Environment variables are project settings, not encrypted secrets.
• Shared project limit. Sticklight Cloud projects count toward the same workspace limit as Studio projects.

FAQs

Is this the same as Cloud Backend?

No. Cloud Backend provides database, auth, and storage for apps built in Sticklight Studio. Sticklight Cloud is edge delivery for code from GitHub. Two different tools that share a workspace.

How is this different from publish in Sticklight Studio?

Publish in Sticklight Studio is one click from a project you build inside Sticklight. Sticklight Cloud is for code you write elsewhere and push to GitHub.

Does it support SSR, API routes, or server workloads?

Not yet. Phase one is static sites. SSR and API routes are on the roadmap.

Can I deploy from Claude Code or Cursor directly?

Today, push to GitHub and Sticklight deploys automatically. Direct MCP-based deploy from Claude Code and Cursor is planned.

How does pricing work?

Sticklight Cloud projects count toward your workspace project limit. The free plan includes up to five projects total, including both Sticklight Studio and Sticklight Cloud projects. Upgrade if you need more.

What happens if I revoke Sticklight’s GitHub access?

The connection is lost and auto-deploy stops. Reconnect from your project settings to resume.

Can I use a private repository?

Yes. Connect your GitHub account and authorize access to your private repos. Sticklight only sees repositories from the installations you configure.