Getting started

Shared service or Dedicated Saible

Saible operates both. Dedicated is available on request: a Dedicated instance serves one organisation alone, in an account Saible owns.

Shared serviceDedicated Saible
Who it servesMany organisations, each in its own database schema, in one Saible region.One organisation alone. A second one cannot be created on it.
Who operates itSaible.Saible, in an AWS account Saible owns and opens for that customer alone. Never in the customer's own account.
Address<your-organisation>.saible.ai<your-organisation>.saible.ai, pointing at the instance and nothing else.
RegionAgreed on the call, set once, never moved.The same: one region per instance.
MailSent by Saible's mail service in the organisation's region.Sent from the instance's own account. Until that account may send to any address, only addresses Saible has verified receive it.
Demo dataShown until the organisation has its own data, labelled Demo data.Never shown.
UsageCredits metered for the organisation.Credits metered in the instance itself.
Shared service or Dedicated Saible · what differs for you
Local gatewhole product,one machinePull requestautomatedchecksMergeevery checkgreenShared servicefirstsaved plan, readDedicatedone at a timestops on failure
How a change reaches your instance · stops at the first failure
  • Find my organisation by emailFinds only an organisation that signs in through its own identity provider. Use the address name.
  • Support access requestsThe admins' side is in place. No support identity exists in the instance yet to raise a request.
  • The assistantNeeds Anthropic models enabled on Amazon Bedrock in the instance's account. Ask Saible whether yours is enabled.
  • One view across instancesEach instance's metrics, alarms and logs stay in its own account.
  • Usage sent to invoicingUsage is recorded in the instance. Nothing sends it to an invoice yet.
Not yet available on a Dedicated instance
Steps
  1. 1The first admin signs in at <your-organisation>.saible.ai with the temporary password from the invitation, and chooses their own.
  2. 2Enrol an authenticator under Settings → Security before anything else.
  3. 3Invite a second admin under Settings → Roles & people. Two people approve an application or a policy change.
  4. 4Register the first application under Control → Registry and install a gateway. The gateway runs in your network either way.
For your agents

This topic is also documented as Agent Skills that your agents can load: dedicated-saible, getting-started, release-gate. Request them from Saible.

Next · Overview · LocationsRegions and locations →