Supported stacks

Whatever you built it in, Rexship runs it.

The languages, frameworks, data stores and infrastructure Rexship takes over and answers for, on Rexship’s cloud or in your own VPC. Not on the list? Tell us what you run and we will map it with your engineers.

Languages

JavaScript, TypeScript, Python, Go, Rust, Java, Kotlin, Scala, C#, F#, PHP, Ruby, Elixir, Erlang, C, C++, Swift, Dart, Clojure, Haskell, Perl, Lua and R.

Any other language runs too, as long as it builds in a container.

Web and service frameworks

The frameworks your services, sites and stores are built on, with the versions you run.

JavaScript and TypeScript
Node.js with Express, NestJS and Fastify; Next.js, Nuxt, Remix, SvelteKit and Astro
Python
Django, Flask and FastAPI
Ruby
Rails
PHP
Laravel and Symfony
Sites and stores
WordPress and WooCommerce
Java and Kotlin
Spring Boot and Quarkus
.NET
ASP.NET Core
Elixir
Phoenix
Go
Gin and Echo
Rust
Actix and Axum

Front ends and mobile

What your customers open, built, tested and shipped through the same pipelines.

Front ends
React, Vue, Angular, Svelte and static sites
Mobile
Builds and tests for iOS and Android apps in Swift, Kotlin, React Native and Flutter, and the back ends behind them

Databases

Every database is monitored and backed up, and can be recovered in another region.

Relational
PostgreSQL, MySQL, MariaDB, SQL Server, Oracle Database and SQLite
Document
MongoDB
Key-value and cache
Redis and Valkey
Wide-column
Cassandra
Search
Elasticsearch and OpenSearch
Analytics
ClickHouse
Vector
pgvector, Qdrant, Weaviate and Milvus

Messaging and streaming

Kafka, RabbitMQ, NATS and Redis Streams, and the producers, consumers and workers built on them.

Data, machine learning and AI

Pipelines
Spark, Airflow and dbt
Storage
Data warehouses and lakes
Jobs
Scheduled and batch jobs
Models
Model serving, and the agents and model-backed services you build

Runtimes and infrastructure

Runtimes
Containers, Kubernetes, serverless functions and virtual machines
Workloads
Web services, APIs, background workers and cron jobs
Infrastructure code
Terraform, OpenTofu, Pulumi, Helm and Ansible
Where it runs
Rexship’s cloud, or your own VPC with keys you hold, in the regions you choose

What running it means

Rexship answers for every stack on this page end to end, not only for its code.

Code
Hosted on the platform, every change reviewed for eight kinds of weakness
Releases
Sealed, signed builds, tested on your suite and released in stages with automatic rollback
Upkeep
Dependencies, runtimes and frameworks kept current, major versions included, and every repair shipped with a regression test
Security
Secrets, dependencies, images and cloud configuration checked continuously, and every endpoint behind Rexship’s edge
Operations
Monitored, scaled to demand and backed up, with recovery to another region, within the budget you set
Incidents
Detected, triaged and answered by Rexship, with a person paged when your policy says so

Not on the list?

Tell us what you run. In the architecture review we map your estate with your engineers, stack by stack, before anything moves.

Rexship then takes it over one system at a time, without a rewrite.

Supported stacks · Revision A