Sanaf AI
Start free
Artificial Intelligence

Openlayer, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Openlayer account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Artificial Intelligence
  • Connects with a key
  • 10 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Openlayer is

Openlayer is an AI quality platform for managing projects, monitoring production data, evaluating tests, and inspecting model and application performance.

You paste in a key from your own Openlayer account. It is kept encrypted, and you can withdraw it from inside Openlayer whenever you like.

How a run works

One message in, the work done in Openlayer.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Openlayer. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Openlayer account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

10 tools it already has

What it can do in Openlayer

These are the ready-made tools your AI employee already has in Openlayer. It is not limited to them, but it never has to be taught these.

  • Get Data SourceReturn one Openlayer monitoring data source, including its backend, monitoring status, record and test counts, and optional project or workspace details.
  • Get Project VersionReturn one Openlayer project commit or version with its processing status, commit metadata, storage URI, and passing, failing, and total test counts.
  • Get WorkspaceReturn a workspace's identity, status, connected-account membership, usage counts, and plan limits. Obtain workspaceid from List Projects first.
  • List Data Source Test ResultsReturn one page of the latest monitoring test results for an Openlayer data source, optionally filtered by test category or execution status.
  • List Data SourcesReturn one page of monitoring data sources for an Openlayer project, optionally filtered by name.
  • List Project Version Test ResultsReturn one page of test results for a project version, optionally filtered by test category, archive state, or result status.
  • List Project VersionsReturn one page of commits and versions for an Openlayer project, including processing status, commit metadata, and passing, failing, and total test counts.
  • List ProjectsReturn one page of projects visible to the connected Openlayer workspace, optionally filtered by name or task type.
  • List Test ResultsReturn one page of results for a test, with optional project-version, data-source, and status filters and optional generated insights.
  • List TestsReturn one page of tests configured for an Openlayer project, with filters for category, archive state, origin version, production-data use, and suggested status.
Access, and who is in charge of it

You stay the boss of your Openlayer account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Openlayer account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Openlayer is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Openlayer and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Openlayer

Can an AI employee really work inside Openlayer?
Yes. It signs in to your own Openlayer account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Openlayer?
No. Nothing moves and nothing is replaced. Your records stay in Openlayer, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Openlayer account?
You paste in a key from your own Openlayer account. It is kept encrypted, and you can withdraw it from inside Openlayer whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Openlayer?
It has 10 ready-made tools in Openlayer today, among them Get Data Source, Get Project Version and Get Workspace. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Openlayer and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Openlayer and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Openlayer?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Openlayer is written down with what it did and when.