FAQ

Stormkit stands out in its capability to host static websites, single-page applications (SPAs), and serverless functions. Its optimization for performance ensures a smooth journey for JavaScript developers. The platform offers a range of features, including dynamic injection of frontend code, instant rollbacks, feature flags, customizable CDN storage, and trigger functions.

Conversely, Heroku provides a broader application platform that accommodates diverse application types, including web apps, APIs, and beyond. It enables developers to deploy applications constructed with a variety of programming languages and frameworks.

Not directly, Stormkit is optimized for serverless deployments and provides a serverless computing environment through its serverless functions feature, which allows you to deploy pieces of code that respond to HTTP requests. These functions are stateless and designed to be short-lived. You can use Nuxt.js functions or use plain functions which has same interface as Node.js. If you are looking for long lived executions please contact with us. We can tailor our platform according your needs.

Certainly! Explore our detailed blog post as an example, demonstrating the integration with Supabase, a PostgreSQL database. By injecting database credentials as environment variables into backend functions, you can seamlessly establish a connection.

If your repository encompasses multiple projects, Stormkit offers two approaches for deployment. Firstly, you can create distinct projects within the same repository and set up automated deployment based on branch naming conventions. For instance, if your repository hosts both frontend and backend applications, establish two projects triggering deployment when branches start with fe- and be- respectively. Configure these settings in the environment's configuration section.

Alternatively, you can create two separate environments within a single app, one for frontend and the other for backend. Utilizing the SK_CWD variable, you can build each project accordingly. As before, deploy triggers can be set up based on branch naming conventions.

Yes, we leverage specific AWS solutions such as Lambda and S3 to enhance our services. Our approach involves utilizing certain AWS services to minimize dependence on AWS. This strategy ensures our platform's adaptability for potential portability to on-premise environments or alternate cloud providers in the future.

As of May 21, 2023, we have made the decision to drop serverless support for Next.js. You can still use Next.js but you won't able to SSR.

At Stormkit, we're dedicated to offering an exceptional user experience through our carefully crafted product. As Stormkit is self-funded, we're investing our energy into developing a solution that truly addresses your requirements.

To maintain our commitment to quality, our cloud solution remains as a paid service, whereas self-hosted users can explore freely the product. This approach enables us to focus on users genuinely interested in exploring our offering.

It's crucial to understand that we're entirely self-funded, without external backing. Our product's growth and development rely solely on revenue generated.

Should you desire an extended trial or a different package, don't hesitate to reach out. As a self-funded entity, we prioritize flexibility in accommodating our customers' financial situations.

Yes.

Yes.

Stormkit employs robust security measures to safeguard your data. This includes encrypting data on disk using the highly secure 256-bit Advanced Encryption Standard (AES-256). Your valuable customer data is backed up hourly to ensure its safety. Additionally, we prioritize security by default through our utilization of HTTPS/SSL protocols.

We're prepared for unexpected traffic spikes. Our platform is designed to scale dynamically, automatically adjusting resources to meet demand. This ensures that your applications remain responsive and available, even during periods of sudden increased traffic.