Skip to main content
Before deploying your first resources on Strettch Cloud, understanding these core concepts will help you organize your infrastructure and manage costs effectively.

​
Understanding Teams

Problem: How do I organize my cloud resources and collaborate with others? Teams are the top-level organizational structure in Strettch Cloud. Every resource you create—compute instances, DNS zones, and more—belongs to a team.

​
How Teams Work

When you create your first account, Strettch Cloud automatically creates a default team for you, named after your first name (for example, “Liberi’s Team” if your name is Liberi). You can create additional teams or join existing ones to collaborate with other users. Team Structure with Multiple Teams:

​
Key Team Principles

  • Resources belong directly to teams: There is no intermediate project layer. When you create a compute instance or DNS zone, it belongs to the team.
  • Users can join multiple teams: You can be a member of several teams simultaneously, each with its own resources and billing.
  • Teams have roles: Teams include roles (owner, admin, member) to control who can manage resources. See the Teams documentation for details on permissions.
  • Teams are isolated: Teams cannot share resources or billing with each other. Each team operates independently.
Violation PolicyIf any team member uses a team resource to commit a violation (for example, illegal activity on a compute instance), all resources belonging to that team will be shut down immediately pending investigation. This may result in a permanent ban.

​
How Billing Works

Problem: When am I charged for my cloud resources? Strettch Cloud uses a pay-as-you-go billing model. Understanding how this works helps you predict and control costs.

​
Pay-as-you-go vs Pay-per-use

Strettch Cloud uses pay-as-you-go, not pay-per-use. Here’s the comparison:
Billing ExampleA compute instance costs 10 RWF per hour. If you reserve this instance for 24 hours (one day):
You pay 240 RWF for that day regardless of whether the instance processes workloads all day or sits idle. Your monthly bill accumulates these daily charges throughout the billing cycle.
Stopping a compute instance does not stop billing. To stop incurring charges, you must destroy the resource. See Resource Lifecycle in SC Compute Overview for details on resource states.

​
Next Steps

Now that you understand how teams and billing work: