Deployments Overview

Deploy your applications using Stormkit with Git integration, automatic deployments, and serverless functions.

What is a Deployment?

Stormkit builds and deploys your application using AWS infrastructure. Static assets are hosted on S3 buckets and served through a CDN, while server-side logic runs on AWS Lambda functions.

Each deployment creates an immutable snapshot of your application that can be previewed, tested, and published to production.

Deployment Methods

There are three ways to trigger a deployment:

1. Git Push

   Enable auto deployments in your environment settings. Stormkit will automatically build and deploy when you push commits to configured branches.

   git push origin main
   

   Stormkit receives the push event, builds your application, and creates a preview deployment with a unique URL.

2. UI Deployment

   Manually trigger deployments from the Stormkit dashboard:

   1. Visit your application
   2. Click the Deploy Now button
   3. Select your environment
   4. Optionally override configuration for this deployment
3. Deploy Trigger API

   Generate a deployment trigger URL for CI/CD integration:

   1. Go to App > Settings
   2. Find the Trigger Deploy section
   3. Click Generate

   Use the generated URL with GET or POST requests:

   curl -XPOST https://api.stormkit.io/hooks/app/:app-id/deploy/:token/:environment-id \
     -H 'Content-Type: application/json' \
     -d '{"publish": true, "branch": "main"}'
   

Keep your deployment trigger URL secure. Do not commit it to version control or share it publicly.

Deployment Infrastructure

Stormkit uses AWS services for hosting:

• S3 Buckets - Static asset storage
• CloudFront CDN - Global content delivery
• AWS Lambda - Serverless function execution
• Load Balancer - Traffic routing and SSL termination

Deployment Types

Static Deployments

Pure static sites with no server-side rendering. All files are uploaded to S3 and served via CDN.

Server-Side Rendering (SSR)

Applications with dynamic server logic run on AWS Lambda functions, with static assets still served from the CDN.

Hybrid Deployments

Combination of static pages, API functions, and server-rendered pages in a single deployment.

Deployment Lifecycle

1. Trigger

   Deployment is triggered via Git push, UI, or API.

2. Queue

   Deployment enters the build queue and waits for available runner.

3. Build

   Runner clones repository, installs dependencies, and executes build commands.

4. Upload

   Built artifacts are packaged and uploaded to S3.

5. Preview

   Deployment becomes available at a unique preview URL.

6. Status Checks

   Optional automated tests run to verify deployment quality.

7. Publish

   Deployment is promoted to production environment (manual or automatic).

Preview URLs

Every deployment gets a unique preview URL:

https://my-app--591950.stormkit.dev

The URL format is: {app-name}--{deployment-id}.stormkit.dev

Preview URLs are permanent and immutable, allowing you to test any deployment at any time.

Environment URLs

Published deployments are available at environment-specific URLs:

https://my-app--production.stormkit.dev
https://my-app--staging.stormkit.dev

Next Steps

Configuration

Configure build settings, environment variables, and deployment options

Auto Deployments

Set up automatic deployments on Git push

How We Deploy

Understand the deployment process and folder structure

Troubleshooting

Solve common deployment issues