CoRoid runs in its own cloud, and on the customer's own infrastructure in private preview. This stage gives the customer an organisation in CoRoid.
In the cloud
There is nothing to install. CoRoid runs and upgrades the service.
- The customer creates the organisation. A person at the customer signs up and creates it, so that the customer owns it from the start. Do not create the customer's organisation with a consultant's account. See Create your account and organisation.
- Choose the plan. On Free, the owner is the only member, so nobody else can join. Professional has unlimited members, and you can add agent slots to it. Enterprise is in private preview. See Plans and pricing.
- Decide where model calls may go. CoRoid's cloud runs in the EU. It has no region outside the EU today. When the customer's rules say that model calls must also stay in the EU, use the EU Only AI profile. It is a real limit, so some models are not available. See EU Only and Low carbon.
- The customer invites the implementers. Each implementer gets a role in Settings → Members, under the access rules for consultants.
Size the agent slots later, from what the pilot shows. See Capacity and agent slots.
On-premises
On-premises installation is in private preview. There is no installation package to download today. Before you plan an installation, contact CoRoid.
The other stages of this guide are the same work wherever CoRoid runs.
Done when
- The organisation exists, and the customer's owner has the Owner role.
- The plan has the members and the agent slots that the pilot needs.
- Each implementer is a member, with an account of their own.
- The discovery document says whether model calls must stay in the EU.
Related
- Security and deployment
- Connect, the next stage