Project & Services Structure
Zerops organizes your infrastructure into three hierarchical levels: projects, services, and containers.
Projects​
A project is the top-level entity in Zerops, functioning as a private network where services can communicate internally and share environment variables. Each project provides essential infrastructure including load balancing, routing, and container orchestration.
Consider your project organization strategy carefully. You can create separate projects for different environments or consolidate multiple applications in a single project to optimize resource usage.
Key Project Features​
Projects provide several important capabilities:
- Private Networking: All services within a project share a secure network
- Environment Variables: Services can access shared environment variables
- IPv6/IPv4 Addressing: Each project receives an IPv6 address, with optional IPv4 addressing
Project Core​
When you create a project, it requires a functioning core that includes:
- Logger and statistics services
- HTTP routing with automatic SSL certificate management
- IP routing with integrated firewall
Zerops offers two core types to match different needs and budgets:
Lightweight Core​
Our single-container solution that packs everything you need to get started quickly. Includes a project controller, L3 balancer, firewall, logger, statistics, and HTTP handling—all in one efficient package. Perfect for development projects and smaller production workloads where simplicity matters. Automatically handles SSL certificates and load balancing without complex setup.
Serious Core​
Enterprise-grade infrastructure designed for mission-critical applications. Separates core services across multiple containers for true redundancy and high availability. Includes redundant project controllers and balancers, dedicated statistics and logging services, and advanced HTTP management. Ideal when your production workloads demand maximum reliability and scalability without compromise.
Features Comparison​
Compare our core infrastructure options side-by-side to find the right fit for your project needs, from resource allocations to available features:
Lightweight Core | Serious Core | |
---|---|---|
Infrastructure | Single container (limited redundancy) | Multi-container (highly available) |
SSL Termination | ||
Automatic Certificate Generation | ||
Proxy / Load Balancer | ||
IPv6 Address | ||
Build Time | 15 hours | 150 hours |
Backup Space | 5 GB | 25 GB |
Egress | 100 GB | 3 TB |
Failover Protection | Limited | Comprehensive |
For detailed pricing information on both core types, visit our pricing page.
Services​
Services encapsulate your containers and provide specific functionality. A project can contain unlimited services, each with its own purpose.
Services in Zerops can be:
- Fully managed: Zerops handles scaling, routing, and repairs automatically
- Partially managed: You maintain control over certain management aspects
Containers​
Containers are the most granular level of the Zerops architecture. Each service consists of one or more containers that work together to deliver functionality.
In High Availability (HA) mode, a service may utilize multiple containers with different roles. For example, a fully managed MariaDB service might use 5 containers: 3 for the database and 2 for proxies.
Containers in Zerops:
- Use predefined images ranging from fully managed databases to customizable Ubuntu environments
- Can be exposed to the public via Zerops subdomains, custom domains, or public ports (for applicable service types only)
- Operate within the service's resource constraints