Skip to main content

Getting Started with Fleet

This page is your on-ramp as an org admin. By the end of it you'll have a Fleet account, an organization with at least one member, a plan selected, and your first shared configuration on its way to members' Harnesses.

Each step links to the detailed page for that topic — come back here whenever you lose the thread.

Step 1 — Create your account​

Go to fleet.kameas.ai and sign up. During sign-up you choose between:

  • Pro — a single seat for an individual practitioner.
  • Team — a multi-seat org you'll share with your team.

You'll pick a plan, enter your payment details, and accept the terms. New accounts get a 14-day free trial — no charge until day 15, cancel any time.

The person who completes sign-up becomes the org owner automatically.

:::tip Already have an account? Skip to Step 2. :::

Full details: Plans & Billing · Accounts & SSO

Step 2 — Sign in and connect SSO​

Once your account is active, sign in at fleet.kameas.ai with the email and password you used to sign up.

If you're on the Team plan and your organization uses Google Workspace or Microsoft Entra, your members will want to sign in with their company credentials rather than a separate password. You can connect your identity provider now under Settings → SSO — email domain discovery means anyone on your claimed domain is routed to your IdP automatically when they sign in.

:::note Enterprise SSO Custom SAML/OIDC (Okta, Azure AD, and others) is an Enterprise-only feature. On Team, Google and Microsoft SSO are supported out of the box. :::

Full details: Accounts & SSO

Step 3 — Create your org and invite your team​

Your organization was created automatically when you signed up. Now add your team:

  1. Open Members in the Fleet dashboard.
  2. Click Invite members, enter your teammates' work email addresses, and assign each a role — admin or member.
  3. Each person receives an invitation email. Once they accept, their account is provisioned and they can sign in to Fleet from the Harness.

A few things to know up front:

  • You can organize members into teams (sub-groups within the org) from the Teams page. Shared context you publish can be scoped to a specific team.
  • Only owners and admins can invite, remove, or change roles. Regular members can read the roster but can't manage others.
  • You can't invite someone directly as org_owner — transfer ownership later via Settings → Transfer ownership after they've joined as an admin.

Full details: Organizations & Teams

Step 4 — Choose or confirm your plan​

You selected a plan at sign-up, but it's worth reviewing what each tier unlocks before you set policy for your team:

  • Pro — personal dashboard, usage analytics, and cost reporting. One seat.
  • Team — org management, member invitations, shared context graph, routing policy, config bundle distribution, tamper-evident audit log, and emergency lockdown. Starts at 10 seats.
  • Enterprise — everything in Team, plus custom Rego routing policies, SAML SSO, cross-team context isolation, isolated Fleet infrastructure, runtime monitoring, and SOC 2 reports. Contact Kameas.

Features like routing policy and emergency lockdown require Team or above. If you're evaluating whether Team meets your needs, the Plans & Billing page has the full comparison table.

To upgrade: Settings → Billing → Upgrade plan.

Full details: Plans & Billing

Step 5 — Publish your first shared configuration​

Once members have accepted their invitations and signed in to their Harnesses, you're ready to push shared configuration.

From the Fleet dashboard, go to Configuration. You can publish any combination of:

  • Routing policy — which AI providers and models members are allowed to use (Team and above).
  • Shared context graph — facts, decisions, and reference material that lands in every member's Harness automatically (Team and above).
  • Config bundles — broader policy and tool configuration distributed to members (Team and above).

When you publish, Fleet packages everything as a signed bundle. Members' Harnesses verify the signature and apply the configuration on the next sync. Members can always see what their Harness has received — there's no hidden mode.

:::tip Starting small? You don't need to publish everything at once. A good first publish is just a routing policy that points your team at the models you've approved. Add shared context as your team builds it up. :::

Full details: Syncing to the Harness

What's next?​

Once your team is up and running, explore:

  • Audit & Telemetry — view the org audit log and (optionally) enable usage analytics.
  • Emergency Lockdown — the break-glass tool for lost or compromised devices (Team and Enterprise).
  • FAQ — common questions from admins and members.