Organizations
An organisation is the top-level tenant in AIchor. Everything else — projects, experiments, engines, version-control providers, storage and users — belongs to exactly one organisation, and organisations are fully isolated from one another. Members of one organisation never see the projects, data or compute of another.
Each organisation has a name and a unique subdomain, and can carry its own branding (logo and colours) and billing currency.
How organisations are created
Organisations are provisioned by the AIchor (InstaDeep) team — there is no self-service sign-up. When an organisation is set up, the AIchor team registers its name, subdomain and branding, and creates the first administrator account. From that point on, the organisation's administrators manage their own projects, engines and members.
Feature flags
Not every organisation has the same set of features turned on. AIchor uses per-organisation feature flags so that capabilities can be enabled or disabled independently for each organisation. These flags are managed by the AIchor team, not from the organisation UI.
Examples of features controlled this way:
| Feature | What it enables |
|---|---|
| Storage management | The storage and bucket management features. |
| FinOps costs | Monetary cost figures in the FinOps page (in addition to resource-usage hours). |
| Switch VCS repository | Switching a project's linked version-control repository. |
SYS_PTRACE | Enable this Linux kernel capability on experiment containers, used by some debuggers and profilers. |
Because features vary per organisation, a capability described elsewhere in this documentation may not be visible in your organisation if its feature flag is disabled. Contact the AIchor team if you need a feature enabled.