Home
Sign in

A project is a workspace inside your organization. It is where you group related work: each project holds its own pools of nodes, its own members, and the providers and network it can use. Many teams create one project per environment (for example "development" and "production") or one per application.

Why projects exist

Your organization can contain several projects, and each project keeps its resources separate from the others. This lets you give different people access to different projects, and keeps one team's nodes from getting mixed up with another's. A project always belongs to exactly one organization; see Organizations for the layer above.

Creating a project

You need an organization first. If you do not have one, create it from the Orgs page (see Organizations).

  1. Go to Projects and click Add Project (or Create a new project).
  2. Choose the Organization the project belongs to.
  3. Enter a Project Name — a human-readable name (for example, "Web Production").
  4. Enter a Project Code — a short identifier used in web addresses and API paths. It must be 2 to 8 lowercase letters or numbers, with no dashes (for example, webprod). The code is suggested from the name, but you can change it.
  5. Click Create Project.

The person who creates a project becomes its owner. Each project code must be unique within the organization. If your organization has reached its limit on the number of projects, the Create Project button is disabled; an organization owner can raise the limit (see Organizations).

What lives inside a project

Open a project to see everything it contains:

  • Pools — groups of nodes. This is where the actual machines live. See Pools.
  • Members — the people who can work in this project.
  • Resource Providers — the infrastructure the project is allowed to run nodes on. See Providers.
  • Networks — an isolated private network for the project's nodes. You do not create this by hand; ORC8R sets one up automatically the first time you deploy a node on a provider that isolates networks.

Project members

Each project has its own member list, separate from the organization's. Open a project and go to its members to add people or change their access. Project roles include owner, member, and viewer, so you can give someone read-only access to a project without letting them change it.

Renaming a project

Open a project's settings to rename it. The project code stays the same, so any web addresses or API paths that use the code keep working.

  • Pools — group and scale nodes inside a project.
  • Nodes — the individual machines.
  • Providers — where a project's nodes run.