This article contains a list of frameworks and languages along with information about whether they work with Kinsta Application Hosting and Database Hosting.

If you do not see the framework or language you would like to use listed here, please contact our sales or support teams.

Adobe Content Server

Maybe. Application and Database Hosting does not currently support applications that require persistent storage. If Adobe Content Server needs any persistent disk storage, we cannot currently host it; if not, we can host it but cannot provide technical support.

Angular applications

Yes. We can host Angular applications; however, you should follow the Static Site Hosting guide.

In particular, static sites require a script called start in their package.json files and use the serve package to serve their static assets. (index.html, styles, fonts, images). Similar to the Gatsby hello world repository.

ASP.NET

Yes. Users can run apps built with Dotnet Core. DotNet Core can be run in Linux containers; see this example.

.NET is moving toward a Core/Cross-platform supported/cloud-ready environment. The ASP.NET Core Runtime Docker hub contains some pre-built Docker containers for Core, and .NET samples have some examples for using typical MS SQL + ASP.NET Core setups with Docker compose.

Astro

Yes. We have a quick start example GitHub repo for Astro.

Cascade CMS

Maybe. You may be able to host Cascade CMS with a Dockerfile, there is a GitHub repository, but it requires a lot of adjustments. You’ll have to know how to write Dockerfiles and understand the Cascade CMS technical requirements. Kinsta cannot provide technical support for this.

CodeIgniter

Yes. CodeIgniter is a PHP-based application, so during the deployment process, Kinsta automatically installs the dependencies defined in your composer.json file.

commercetools

Yes. commercetools uses Java, JavaScript, and PHP and can be run on Application hosting.

Database replicas

No. We do not currently provide database replicas.

Dedicated IP Addresses

No. We do not provide dedicated IP addresses. Each new deployment may get a pod scheduled on a different host, which results in a different IP address. A change in IP address can also happen if Kubernetes needs to move a pod to another host because of resource consumption or if the node pool it’s on is in the process of an upgrade.

Deno

Yes. We have a quick start example GitHub repo for Deno.

Direct SSH access to pods

No. We do not currently provide direct SSH access to pods; however, this is something we hope to develop in the future. For a database, you can use external connections to access the data.

Django

Yes. We have a quick start example GitHub repo for Django. You can follow this guide on setting up a Django application at Kinsta.

Docusaurus

Yes. We have a quick start example GitHub repo for Docusaurus. You can follow our guide on how to set up a static site with Docusaurus.

Flask

Yes. We have a quick start example GitHub repo for Flask.

Flutter

Yes. If the Flutter app is a web application and has a Dockerfile, you can host it on application hosting.

Gatsby

Yes. We have a quick start example GitHub repo for Gatsby.

Go

Yes. We have a quick start example GitHub repo for Go.

Headless applications such as sanity.io

Yes. The backend would use the Sanity platform and the front-end ReactJS.

For this to work on application hosting, you must modify scripts in package.json in the Sanity project to look as follows:

"scripts": {
"dev": "npx -y @sanity/cli start",
"build": "npx -y @sanity/cli build",
"start": "npx -y serve dist"
},

You also need to add the MyKinsta temporary domain name (their-app-name.kinsta.app) that is assigned to the app at the project/API/CORS origins settings.

Incremental Static Regeneration on Next.js

Yes. This works on application hosting; for more information about how to configure the app, please refer to this Next.js article.

Jamstack

Yes. We have the following example GitHub repos:

Java

Yes. We have a quick start example GitHub repo for Java.

Joomla

Maybe. Application hosting only supports stateless applications, and Joomla was not designed for use in a stateless environment. However, it is technically possible to run Joomla as a stateless app. There is a plugin that can store the static files on S3, and there is an official Joomla docker image.

Laravel

Yes. We have a quick start example GitHub repo for Laravel.

Magento

No. Magento requires persistent disk storage, which we don’t currently offer as part of Application hosting.

Mastadon

Maybe. It is possible to run Mastadon on Application hosting, but it requires a lot of resources, so the cost to run it may be high. You would likely need the 4GB pod as it uses ~1.5GB RAM. There is also no persistent storage yet, so if your pod is cycled or moved, it would need to re-fetch everything. The pods don’t restart often, but when they do, the filesystem resets back to the original container filesystem.

Mobile Apps

Maybe. It depends on the app; you can host the backend of a mobile app with Application hosting but not the building or distributing of the mobile app itself.

MODX

Maybe. MODX is a PHP open-source CMS platform, however, it may require persistent storage which Application hosting does not currently support. If the site can be run without persistent storage it can be hosted on Application hosting.

Moodle

No. Moodle requires a persistent storage/volume to function properly; it cannot function as a stateless application (where no critical files are written to the filesystem so the application can function properly). That means we cannot support this, as each deployment would erase some data that Moodle relies on.

MSSQL

No. MSSQL requires persistent storage, which we don’t currently offer as part of Application hosting. When persistent storage is available in Application hosting, it should be possible to run, according to this article.

n8n

Yes. According to Docker n8n Documentation, it recommends persistent storage as best practice, but it is not explicitly required:

“It is important to still persist data in the /root/.n8n folder as it contains n8n user data and, even more importantly, the encryption key for credentials… …Persisting the /root/.n8n directory even when using alternate databases is the recommended best practice, but not explicitly required.”

Therefore it should work on Application hosting without persistent storage if you use a database, too; however, it will work best when persistent storage is available within Application hosting.

NodeJS

Yes. We have the following quick start example GitHub repos for NodeJS:

We have different guides you can follow:
Set Up a Node.js Application
Set Up a Node.js Application With a Dockerfile
Set Up a Node.js Application To Send Emails

NuxtJS

Yes. We have a quick start example GitHub repo for NuxtJS.

PHP

Yes. We have the following quick start example GitHub repos for PHP:

You can follow this guide on how to set up a PHP application at Kinsta.

Prestashop

No. The official docker-compose file specifies a persistent storage volume, and we do not currently support persistent storage.

QPDF

Maybe. QPDF is a command-line tool. The website also states this:

QPDF is included in most Linux distributions and many other software distributions.

This indicates they have a Dockerfile-based application, which relies on the CLI tool. There are some public repositories on GitHub which install QPDF within the Dockerfile with some commands; here is an example. If you add the same commands to the Dockerfile, you will be able to use QPDF; however, we have not tested it on our platform.

QPDF is a C++ lib and may require additional components installed on the Linux instance so that it can be compiled successfully.

Ruby

Yes. We have a quick start example GitHub repo for Ruby on Rails.

Scala

Yes. We have a quick start example GitHub repo for Scala.

Shopify

Maybe. All the repos in the Shopify github are for different parts of their application; you can’t self-host the entire site. However, you can use Hydrogen to create a self-hosted custom storefront, which would be usable on Application hosting if you create a Dockerfile for it.

Shopware

Yes. Shopware is an open headless commerce platform powered by Symfony 5.4 (PHP) and Vue.js 2.6 and can run on Application hosting.

Spider Storage Engine in MariaDB

No. This is currently not supported as uses a higher level of database clustering.

Statamic

Yes. Statamic is based on Laravel, which means that it’s a regular PHP-based application, so during the deployment process, Kinsta automatically installs dependencies defined in your composer.json file.

Symfony

Yes. Symfony is a PHP framework to create websites and web applications and can run on Application hosting.

SvelteKit

Yes. SvelteKit is a UI framework that compiles your components to vanilla JavaScript and can be run on Application hosting.

Velo by Wix

No. Velo does not have a self-hosted option. You can only use Wix Cloud, so you cannot access the code to use on our Application hosting.

VuePress

Yes. We have a quick start example GitHub repo for VuePress.

Windows Server Applications

Maybe. If the application can be run in a Linux container, you may be able to host it within Application hosting.

Wix

No. Wix is not open source, so you can’t access the code to move the application or website onto our hosting services.

Yarn

Yes. Yarn is supported for Application hosting.