At Codenteam, our mission is to provide a secure, efficient, and equitable environment for running and managing code. Our infrastructure is designed with a focus on isolation, security, and fairness to ensure that every customer receives reliable service.
1. Container Isolation & Code Handling
Codenteam operates a pool of fully isolated containers. In accordance with our strict policy of never storing code permanently, we adhere to the following procedures:
- On-Demand Code Cloning: Code is cloned only when needed within an isolated container.
- Single Execution Instance: Each container runs a single code clone during its lifecycle.
- Ephemeral Containers: Once the code execution completes, the container is destroyed immediately, ensuring no residual data remains.
This approach not only enhances security and isolation but also minimizes the risk of unintended code persistence.
2. Infrastructure Considerations
The rigorous isolation and ephemeral container strategy we employ comes at a significant cost. Because each container is a dedicated, short-lived environment, the process of cloning, running, and destroying containers places considerable demands on our infrastructure. These costs necessitate the implementation of fair usage measures to maintain the quality of service for all customers.
3. Fair Usage Framework & Quotas
To prevent any single customer from adversely affecting our service levels, Codenteam has established fair usage guidelines that are built on top of our quota system. These quotas are determined by market averages and are designed to reflect typical developer activity. The key elements of our fair usage framework include:
- Developer Identification: Every unique combination of name and email in the code is considered to represent a single developer.
- Market Average Metrics: Each developer is expected to maintain a number of lines of code, keep specific storage in the repository, and manage a specific number of dependencies. These figures are benchmarked against market averages and are updated annually by Codenteam. The exact metrics, however, remain undisclosed.
- Usage Quotas: Our system enforces quotas based on these market average expectations. This ensures that resource usage remains within acceptable limits, thereby protecting the service quality for all users.
- Storage: Any codebase is limited to a maximum of 10GBs of storage, except for Enterprise customers.
4. Ensuring Equitable Access
Our fair usage measures are designed to balance resource allocation across our customer base. In practical terms, this means that if a customer’s code execution demands significantly exceed the average expected usage, the system may:
- Throttle Resource Allocation: Limit the duration or intensity of the code execution environment.
- Enforce Quota Restrictions: Temporarily suspend or limit additional resource consumption until normal usage patterns resume.
These measures help prevent any single customer from monopolizing our infrastructure resources, ensuring a consistent and reliable service for everyone.
5. Policy Updates & Transparency
Codenteam is committed to transparency and continuous improvement. Our fair usage metrics are reviewed and updated on an annual basis to reflect evolving market trends and technological advancements. We reserve the right to adjust quotas and operational policies to maintain optimal service levels and infrastructure stability.
6. Contact & Support
If you have any questions or concerns regarding our fair usage policy, or if you believe your usage may require special consideration, please contact our support team at support@codenteam.com. We are here to help and ensure that your experience with Codenteam remains productive and secure.
7. Examples
Example: Dependency Count
- Scenario: A customer has 5 registered developers.
- Observed Usage: The project is found to be using 1,500 direct dependencies.
- Action: With the dependency count much more than the market average, fair usage policies require a cap on this usage to maintain equitable resource allocation.
Example: Storage Consumption
- Scenario: A customer has 4 registered developers.
- Observed Usage: A container session is consuming 12GB of storage.
- Action: A 12GB usage represents a much higher value than expected for 4 developers, and exceeds the limit of 10GBs, triggering limitations to protect overall system performance and stability.
Example: Lines of Code (LOC)
- Scenario: A customer has 3 registered developers.
- Observed Usage: The customer’s codebase contains 1,000,000 lines of code, which is far above the average repository size for 3 developers.
- Action: Since this exceeds the market average by more than threefold, restrictions will be applied to ensure that resource usage remains balanced across all users. The analysis will be canceled, and creating new analysis will be forbidden until upgrading to a higher tier.
By using Codenteam’s services, you acknowledge and agree to adhere to the terms of this fair usage policy, designed to maintain a balanced, secure, and efficient coding environment for all our users.
