Organizations and projects

Organizations

An organization (ID o-…) is your company, team or personal account on TebibHost. It holds:

• the wallet and everything about billing (one wallet for all its projects);
• the people and machines: users, groups, service accounts, roles and their policies;
• its country, home region and trust tier (which sets its limits);
• its projects.

One person can belong to several organizations and can own up to 3. Switch between them in the console’s organization switcher or with tebib --org / TEBIB_ORGANIZATION.

Projects

A project (ID p-…) is where resources live: VMs, volumes, snapshots, SSH keys, VPCs, subnets, security groups, NAT gateways and public IPs. Projects are the isolation boundary:

• each project gets its own private network (a default VPC), unreachable from other projects;
• each has its own quotas, on top of the organization’s totals;
• policies can be attached for one project, so a team can run its project and see no other;
• usage and cost are reported per project on the statement.

Use separate projects for production and staging, or for each client you host for.

tebib project create staging --tag env=staging --wait
tebib project list
tebib project quotas p-0123456789ab

Deleting a project

A project must be empty to be deleted: delete its VMs, volumes, snapshots, public IPs, NAT gateways and extra VPCs first. Its default network goes with it.

tebib project delete p-0123456789ab --yes --wait

Tags

Most resources take tags, key=value pairs (for example team=web, env=prod). Tags help you filter and report, and policies can use them: allow a team to manage only resources tagged with its name, or require a tag on everything created.