Yekar.AI Console
The Console is enabled per account, on request. Ask Yekar.AI to grant your team access at console.yekar.ai.
Once you are provisioning organizations through the Partner API, you are running a fleet. The Console is where you see it: every platform you operate, every organization under it, and what each one is actually doing right now - without opening a single customer's workspace.
It is a separate surface from the product at console.yekar.ai, with its own sign-in. Your engineers do not need a seat in any customer organization to use it.
Sign in
Sign in with Google. Access is granted per account by Yekar.AI, so the people you name get in and nobody else does - there is no self-serve signup and no shared credential to rotate.
The Console session is entirely separate from a product session. Signing in here grants nothing in any tenant workspace, and a product session grants nothing here.
Overview
The landing screen answers "is anything wrong" before you have to ask a question. It surfaces what is worth your attention across every platform you operate - organizations with failing runs, extraction backlogs, and platforms with no release cut yet.
If nothing needs you, it says so plainly rather than inventing a dashboard.
Platforms
One row per platform you operate, each with its latest release and the size of its fleet. Selecting a platform opens its fleet.
The fleet
Every organization provisioned under that platform, filterable and searchable, with the numbers that tell you which ones to look at:
| Column | What it tells you |
|---|---|
| Organizations | The provisioned tenants under this platform |
| In flight | Work running right now |
| Failure rate | How much of the recent work failed |
| Files extracting | Knowledge still being processed |
| Last activity | When this organization last did anything |
| Latest release | Which release the organization is on |
Filters are URL-backed, so a filtered fleet view is a link you can paste to a colleague.
Organization detail
Open one organization to see its agents and flows, its recent work, and the controls you need to support it:
- Manage workers - vouch one of your own people into the organization with the permissions they need, so they can act with a real identity and a real audit trail rather than a shared login. See Workers.
- Start session - open a support session against the organization. See Support sessions.
- Login visibility - control whether the organization's own sign-in door is shown.
- Delivery configuration - where this organization's alerts go: mail, webhook, or both. See Alert webhooks.
- Revoke standing - withdraw a worker's access when they no longer need it.
Every one of these is audited. A vouched worker acts as themselves, so the record names a person rather than a platform.
What the Console is not
It is not a way into a customer's data by the back door. Everything here runs through the same follower-organization ownership chain and the same permission model as the Partner API - the Console is a faster way to reach it, not a wider one.