Skip to main content

Environments Overview

Environments in Thevenin allow you to deploy and manage applications across different stages of your development lifecycle. This section covers how to create, configure, and manage environments effectively.

What is an Environment?​

An environment is an isolated deployment space where your applications run. Each environment has its own:

  • Resource allocation (CPU, memory, storage, Bandwidth)
  • Configuration (environment-specific settings)
  • Application instances (running containers)
  • Network settings (ports, domains)

What are Environment Tiers​

Each Environment is created within one of Thevenin Tiers. Each Tier has its prupose:

Dev: Aimed at companies needing a platform to develop products and show them to investors, focusing on speeding up development at the best price.

Prod: Designed for companies requiring a robust, safe, and scalable platform for their production services, offering guaranteed service uptime.

Enterprise: Suited for large enterprises looking to develop new projects, offering customized solutions that integrate with existing infrastructure and business needs.

Environment Features​

Isolation​

Each environment is isolated from others:

  • Separate resources and data
  • Independent configurations
  • No cross-environment interference
  • Security boundaries

Resource Management with Resource Quotas​

Control max computational resources per environment:

  • CPU allocation: Cores dedicated to this environment
  • Memory limits: RAM available for applications
  • Storage quotas: Persistent storage capacity
  • Network bandwidth: Ingress and Egress Data transfer limits

Managing Environments​

Viewing Environment Status​

The environment dashboard shows:

  • Running Applications: Active containers
  • Resource Usage: CPU, memory, storage metrics
  • Health Status: Overall environment health
  • Recent Activity: Deployment history

Updating Configurations​

Modify environment settings:

  1. Navigate to environment details
  2. Click "Edit Environment"
  3. Update settings
  4. Save changes

Common Environment Use Cases​

Environments in Thevenin can be used for different use cases and patterns including but not limited to:

Development Environments​

  • For active development and testing
  • Rapid iteration and frequent updates
  • Lower resource allocation
  • Relaxed security policies

Feature Environments​

  • Feature-specific testing
  • Customer demos
  • Performance testing
  • Training environments
tip

We recommend to create both Development and Feature Environments in the Dev Tier, since it is designed to be cost efficient, unless you need the compliance guarantees of Prod and Enterprise Tiers for your Dev Environments as well.

Staging Environments​

  • Pre-production testing
  • Mirrors production configuration
  • Integration testing
  • Final validation before release

Production Environment​

  • Customer-facing deployments
  • Highest reliability and performance
  • Strict security measures
  • Careful change management
warning

We recommend creating Production Environments ONLY in the Prod or Enterprise Tier since these have uptime guarantees.

Troubleshooting​

Resource Exhaustion​

Symptoms: Applications crashing or slow performance

Solutions:

  • Increase resource quota
  • Scale down or remove unused applications
  • Optimize application resource usage
  • Check for resource leaks

Next Steps​

Learn more about working with environments: