Accounts, projects, environments and services

Narration uses an AI-generated voice.

[00:00] Where we're going

By the end of this video, you'll know where everything you run on ComputeSphere lives, and how to find it. It all sits in one chain. Learn it once, and every screen makes sense.

[00:12] The chain

At the top is your account. That's who pays, and who's in. Inside it, a project. One project holds one product, like a shop. Inside the project, environments. Say, staging and prod, each one a separate copy. And inside each environment, the services. Each one is a running part of your app, like a web server, or a background worker. Every service runs on spherelets. Each spherelet is one running copy. Each level lives inside the one above it. That's the whole idea.

[00:50] Account

Here it is in the console. This is the account overview. Your account's name sits down here, with your role. This one's the owner. The account is where billing lives. One subscription, one card, one set of invoices. It's also where your teammates join.

You can belong to more than one account, say your employer's and your own. Each one bills separately.

[01:17] Project

Next, projects. This account has one project, savanna. A project groups the services that make up one product. It doesn't run anything, or cost anything, by itself.

Open it, and here's what's inside. Its services on the left, and its environments on the right. A good rule: if two things ship and break together, they belong in the same project.

[01:44] Environment

This project has one environment, called dev. An environment is an isolated place for services to run. It has its own network, secrets and limits. So production can't read a staging password. And every service lives in exactly one environment. Here's ours, lagoon, a web service. Want the same app in staging and in prod? That means deploying it twice, once into each.

[02:13] Service and spherelets

Now the service itself. It's Running, and it has its own web address. Look at the path at the top. Project, then service. And its environment is right here, under its name. This is the deployment ID. It identifies this service, in this one environment.

And in its settings, here are its spherelets. One Flex spherelet. That's one running copy of the app. You'll learn more about spherelets later in this module.

[02:44] Recap

So, a quick recap, with what we just saw. Your account pays, and holds your team. A project holds one product. An environment is one isolated copy of it. And a service is one running part, on its spherelets. Find that chain, and you can find anything.

Now try it on paper. Pick an app you've built, or one you want to build. Write down its project, the environments you'd want, and each service it needs. I'll see you in the next lesson.