Strapi

Deploy Strapi on a VPS in One Click

CMS & websites

Open-source headless CMS with auto-generated REST and GraphQL APIs, self-hosted on your own server.

  • Ready in ~5 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (5.x)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
2 GB
License
MIT
Addressing
IPv4, IPv6
GitHub
73,000
Deployment~5 min
Open source & self-hosted
VPS plans

Choose a VPS plan for Strapi

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month

  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month

  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month

  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month

  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month

  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month

  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month

  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month

  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with Strapi

Strapi self hosted is an open-source, API-first CMS built on Node.js that separates content management from the frontend completely. Editors define content types through a visual builder, and Strapi turns them into structured REST and GraphQL endpoints automatically — ready for a Next.js storefront, a mobile app, or a kiosk display to pull from the same source. It fits teams pushing content to more than one channel at once: a marketing site, a product catalog, an app backend running in parallel.

What separates it from Contentful or Sanity is ownership. Nothing about your schema, your media files, or your API traffic sits on someone else's infrastructure or counts against a usage-based bill. Strapi vps hosting keeps the database, the admin panel, and root access to the whole stack in your own hands — which matters the moment your content volume or API call count outgrows a SaaS free tier.

The applications screen of the control panel with one-click install

Strapi features

A server surrounded by app icons — applications running on a VPS

Strapi installation on a VPS gives you the full community edition — nothing is stripped down compared to what you'd get from a managed setup. Here's what ships with it once you install Strapi on VPS:

01

Content-Type Builder

Visual editor for defining collections, single types, and reusable components without writing schema code.

02

Auto-generated REST & GraphQL APIs

Every content type gets working CRUD endpoints the moment it's saved.

03

Role-Based Access Control

Permissions set per role, down to individual fields and content types.

04

Media Library

Built-in asset management with support for S3 and Cloudinary as storage providers.

05

Draft & Publish

Content can be saved as a draft and published separately, with revision history.

06

Internationalization (i18n)

Multilingual content structures available out of the box.

07

Webhooks

Outbound notifications to external systems whenever content changes.

08

Plugin system

Extend Strapi with official plugins or write custom ones against its API.

Requirements

Which server to run it on

Minimum requirements for Strapi and the configuration worth starting with.
Minimum
  • CPU1 vCPU
  • Minimum RAM2 GB
  • Disk20 GB
Recommended
VPS Basex
  • CPU2 vCPU
  • Minimum RAM2 GB
  • Disk40 GB

Installation is free — you only pay for the server

Getting started

How to deploy Strapi

Three steps and the app is running on your server.
Step 1
Choose a server

Node.js and the database (PostgreSQL or MySQL) can handle the workload even on a compact plan. Choose a VPS for Strapi with sufficient memory headroom if you plan to use a media library with large files.

Step 2
Pick the app

Choose the Strapi one-click install from the catalog. The template deploys the backend, database, and admin panel in a single setup, without requiring manual Node.js configuration.

Step 3
Get your credentials

On your first visit to /admin, you’ll need to create an administrator account yourself — Strapi does not provide a preset password.

Why us

Why Host Strapi on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
A Strapi project usually needs a staging environment before every schema change hits production — spinning up a fresh instance in minutes means you can test content-type migrations without touching the live API.
Free installation
Setting up Strapi's Node.js runtime, database, and admin panel by hand takes real time even for an experienced backend developer — hosting for Strapi with a pre-built template skips that without adding to your bill.
DDoS protection
Once your Strapi API feeds a live storefront or public app, every consumer of that API goes down the moment the server does — DDoS protection keeps the content backend answering requests during a traffic spike or an attack.
Control and support
Node.js version upgrades, database tuning, and plugin conflicts are the kind of issues that need shell access, not a support ticket queue — root access plus engineers on call means you can actually fix them.
99.9% uptime with SLA compensation
A frontend built on Strapi's API has no fallback content if the backend is unreachable — the uptime guarantee protects the one dependency your whole site or app can't work without.
Flexible payment
Agencies running Strapi projects for multiple clients bill differently depending on the contract — invoicing for legal entities matches how that work actually gets paid for.
What to choose

Strapi: Self-Hosted vs Cloud — Which to Choose

We compare cost, control over your data and limits, so the choice is an informed one.
Strapi Cloud
Self-hosted on LeneexRecommended
Resources and limitsPlan-based limits, including monthly API request quotas and asset storage capacityDedicated CPU, RAM, and storage exclusively for your project
Control and accessAccess is restricted to the admin panel and project settings, with the underlying infrastructure hiddenRoot access to the server, with full control over Node.js and the database
Feature limitsSome features (advanced roles, audit logs) are available only on higher-tier plansFull access to the Community Edition, with no restrictions on plugins or custom integrations
ScalingAutomatic scaling, subject to the limits of the selected planManual VPS plan upgrades, without competing with other users for shared resources
CostCosts increase with the number of requests, bandwidth usage, and storage requirementsFixed server pricing regardless of traffic growth
Who it fitsIdeal for teams that prioritize a fast setup without server administrationIdeal for projects with predictable or high API workloads and teams that need full control over their technology stack

Strapi Cloud is the official managed hosting service from the Strapi developers, so this is a direct comparison rather than one against an averaged SaaS alternative. Self-hosting becomes more cost-effective when the API handles a high volume of requests or media storage grows rapidly, since VPS pricing is not tied to traffic. Strapi Cloud, on the other hand, frees the team from server administration — a trade-off in the opposite direction.

Frequently Asked Questions about Strapi on VPS

What people ask most about Strapi and our servers.

  • Yes — export the PostgreSQL/MySQL database and the uploads or media storage folder from the old environment, then import both into the new one, since Strapi vps docker deployments read the database and asset paths the same way regardless of provider.

  • The database, media library, and admin configuration stay untouched during a plan upgrade — only the server's CPU and RAM allocation changes, so no migration step is needed.

  • It depends more on content volume and media file sizes than on user count — a small team publishing text-heavy content runs comfortably on an entry-level plan, but a media-heavy catalog with a high-traffic public API needs more RAM and disk I/O headroom.

  • Updating Strapi itself, plugins, and the underlying Node.js runtime is the customer's responsibility, since self-hosting means the deployment stays under your control rather than being patched automatically by a managed provider.

What's preconfigured out of the box

After a one click automation Strapi deployment, the Node.js runtime and the database (PostgreSQL or MySQL, depending on the template) are already linked and running — you don't configure the connection string manually. The admin panel and the API run on the same Node.js process by default, listening on Strapi's standard port 1337 unless the template routes it behind a reverse proxy.

First login

Strapi doesn't ship with a default admin password — the first time you open the admin panel at /admin, it shows a registration form where you create the first administrator account yourself, with your own email and password.

Until that first account is created, the admin panel is open to whoever reaches it first — creating the account immediately after deployment closes that window.

Practical first steps

Environment variables — APP_KEYS, API_TOKEN_SALT, database credentials — are what Strapi uses to sign sessions and connect to the database. Once logged in, the first practical task is usually creating your first content type through the Content-Type Builder — everything else, including the REST and GraphQL endpoints, gets generated from that.

Deploy Strapi in about 5 minutes

Choose a server — we do the rest: install, configure and send you the credentials.