Skip to main content

Understanding Molnett

The Container-First Approach​

Molnett treats containers as the fundamental unit of deployment. If your application runs in Docker, it runs on Molnett. This container-first design means you maintain full control over your application environment while we handle the underlying infrastructure.

Unlike traditional PaaS platforms that force you into specific frameworks or runtimes, Molnett accepts any containerized application. You package your code exactly how you want it, and we execute it reliably at scale.

Deployment Architecture​

When you deploy to Molnett, your container runs inside a Firecracker MicroVM for enhanced security isolation. Each service gets its own network endpoint with automatic HTTPS termination. The platform handles service discovery, so your containers can communicate with each other using simple DNS names.

You're charged only for active compute time when your containers are running and processing requests, not for idle capacity.

Environment Model​

Molnett organizes your applications using a three-tier hierarchy:

  • Tenants represent your organization
  • Projects group related services together
  • Environments separate different deployment stages (development, staging, production)

Each environment is completely isolated. You can deploy the same application to multiple environments without any interference. This makes it safe to test changes in development while production runs stably.

Security and Compliance​

The platform uses Firecracker MicroVMs to provide stronger isolation than traditional containers. Each application runs in its own micro-virtual machine, protecting against container escape vulnerabilities.

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

Operational Model​

Molnett handles operational concerns automatically. SSL certificates are provisioned and renewed automatically. Monitoring and logging are built-in. Updates deploy with zero downtime using rolling deployments.

The platform provides secrets management for sensitive configuration like API keys and database passwords. Secrets are encrypted at rest and injected securely into your containers at runtime.

This operational automation means your development team can focus on building features rather than managing infrastructure. You get enterprise-grade operations without needing dedicated DevOps engineers.