Stormkit LogoStormkit Logo WhiteStormkit


You can easily deploy your applications through the Web UI. To do so, login to Stormkit, click on your application that you'd like to deploy, select the environment and hit deploy now button. It will start the build process.

Every build on Stormkit is run in an isolated environment. The node version is 10.x, same as lambda runtimes.

Build configuration

The build configuration is very straightforward. You can access it by clicking on My application > My Environment > Edit. Here is a table which describes what each field does.

Field nameDescription
Entry fileSpecifies the entry file for the server side application. Leave empty if you don't need server side functionality. Enabling this will tell Stormkit to host your server application in lambdas. Static assets that will be used on the client side will be still served from our CDN.
Public folderThe path to the public folder where static assets are located. The path is relative to the repository root.
Build commandThe build command to build your application. If you're not using a framework like Nuxt.js, we will try to locate your webpack configuration and build the server side on top of this when entry file is enabled.

You can chain multiple commands with a logical && operator. They will be displayed as multiple steps in your deployment logs.
Environment variablesThe environment variables that will be available for the build. Specify each variable in a separate row by pressing Enter key. These variables will be available to all of your commands throughout the deployment. Variables that are not used in your client side application will never be exposed to your clients.

Static sites

To deploy your static website simply leave the entry file empty in the build configuration.

All your assets will be served from our CDN, which is backed by the powerful Amazon S3 buckets. Deleting a deploy will also remove associated the files from the bucket.

Dynamic sites

If you need dynamic behaviour, such as fetching and rendering user data on the server side, simply define an entry file in the build configuration.

Once you define an entry file, all your server files will be hosted on lambda functions. The public assets will continue to be served from the CDN. Stormkit is smart enough to distribute the files accordingly.

The entry file is expected to export a function which receives a Request and Response object as arguments. The function is expected to return a response within 15 seconds. To return a response, simply use the Response.sendmethod.import React from "react"; export default (req, res) => { res.send("Hello world"); };


The deployment package will be zipped in order to be deployed to the lambda function. The zip file should not exceed 50mb zipped, and 250mb unzipped. These limits apply per deploy, not per app.


You can trigger deployments using the hooks endpoint. To generate a new endpoint that will listen for GET and POSTrequests and trigger deployments, simply go to your App > Settings and find the Deploy Triggers section and click on the generate button.

Successful calls to this endpoint will return a 200 status code with the Content-Type header being set to application/json.