Docker or Git Deploy
Push your code or a pre-built Docker image. We handle the build and deployment process automatically.
Deploy your NestJS applications to a managed Docker platform. Includes PostgreSQL, Redis, and persistent volumes out of the box. No server management required.
# docker-compose.yml
services:
api:
image: my-nestjs-app
environment:
- NODE_ENV=production
- DATABASE_URL=${DATABASE_URL}
- REDIS_URL=${REDIS_URL}
ports:
- "3000:3000"
db:
image: postgres:16
volumes:
- db_data:/var/lib/postgresql/dataNestJS is a progressive Node.js framework for building efficient, reliable, and scalable server-side applications. Unlike simple Express scripts, NestJS apps are often structured, enterprise-grade systems that require a robust hosting environment.
While NestJS can run in serverless environments, it is designed as a long-running application framework. It maintains a dependency injection container, database connections, and often WebSockets or microservices listeners. Hosting it on a platform designed for long-running containers ensures optimal performance and avoids "cold start" latency.
NestJS is built with TypeScript. This means your hosting pipeline needs to handle the compilation step (npm run build) to generate the JavaScript that actually runs on the server (typically in dist/main.js). A container-based approach handles this build process cleanly and consistently.
Modern NestJS deployment relies on standard containerization practices:
Dockerfile typically has a build stage (installing dev dependencies and compiling TS) and a production stage (copying dist/ and installing only production dependencies).@nestjs/config to load configuration from environment variables (.env), keeping secrets secure and out of the codebase.We provide a managed platform that maps directly to the standard NestJS architecture.
Push your code or a pre-built Docker image. We handle the build and deployment process automatically.
Spin up managed PostgreSQL, MySQL, or Redis instances alongside your app with a single click or line in your compose file.
Mount volumes for your uploads or local database files. Data persists across deployments and restarts.
All data and workloads are hosted in Germany (Falkenstein), ensuring low latency for European users and GDPR compliance.
"Free" hosting usually comes with significant caveats, which can be particularly problematic for the heavier memory footprint of a NestJS application compared to a simple Express app.
Free tiers are excellent for learning and prototypes but often break for real-world applications. Hostim.dev offers a preview tier for testing, but our focus is on reliable, paid production hosting with predictable pricing.
You might see terms like "web hosting" and "app hosting" used interchangeably, but they refer to different paradigms.
Traditional Web Hosting (Shared): Designed for PHP/WordPress. It rarely supports running a custom Node.js process, let alone the build steps required for NestJS.
App Hosting (PaaS): Designed for modern applications. Provides the necessary environment for containers, build processes, and service orchestration. This is what Hostim.dev provides.
The practical workflow on a container-based platform.
Dockerfile runs npm run buildand starts the app with node dist/main.NODE_ENV, DATABASE_URL, and PORTin the dashboard.Get your NestJS application running in minutes.
You can create free MySQL, PostgreSQL, Redis databases, and persistent volumes. App containers start at €2.5/month. Each user gets one 5-day trial project with everything included – apps, DBs, volumes, metrics.
Yes. Paste your Docker Compose YAML and we'll generate the services automatically. You can also deploy from a Dockerfile or Git repository (repo should have Dockerfile so our system can build the image).
On bare-metal servers located in Germany. We do not use AWS, GCP, or other large cloud providers – your data stays in the EU.
No. Hostim.dev removes Kubernetes complexity. You manage apps, databases, and resources – not clusters or YAML.
Right now, each account manages projects individually. Multi-user roles and team collaboration are planned – we're actively listening to early users to shape this.