Skip to main content

Key Features

Simple Container Deployment​

Molnett accepts any Docker container and runs it with minimal configuration. Define your service in a YAML file, deploy with molnctl, and your application is live with HTTPS endpoints automatically configured.

The platform handles networking, SSL certificates, and service discovery automatically. You don't need to configure load balancers, manage certificates, or set up complex routing rules.

Environment Management​

Create isolated environments for development, staging, and production using the same deployment process. Each environment is completely separate, so you can test changes safely without affecting other deployments.

Deploy to any environment with a simple command:

molnctl deploy --env staging
molnctl deploy --env production

Secure by Design​

Every container runs inside a Firecracker MicroVM, providing stronger isolation than traditional container platforms. This protects against container escape vulnerabilities while maintaining high performance.

All infrastructure runs within EU data centers, ensuring GDPR compliance by design. Your data never leaves European borders, simplifying compliance for European companies.

Secrets Management​

Store sensitive configuration like API keys and database passwords securely using Molnett's built-in secrets management. Secrets are encrypted at rest and injected into your containers at runtime.

# Store a secret
molnctl secrets create database-password --env production

# Reference it in your service definition
secrets:
  - key: DATABASE_PASSWORD
    value: database-password

Monitoring and Observability​

Access application logs through the CLI or web interface. Molnett collects essential metrics including CPU usage, memory consumption, and request counts.

# View logs in real-time
molnctl logs my-service --follow

# Access previous logs
molnctl logs my-service --previous

Transparent Pricing​

Pay only for active compute time when your containers are running and processing requests. No charges for idle capacity or complex pricing tiers.

The pricing model is straightforward:

  • CPU time per second
  • Memory usage per second
  • Storage usage per second

This typically results in 40-70% cost savings compared to always-on instances, especially for development and staging environments that sit idle most of the time.