Sanaf AI
Start free
Developer Tools

Convex, 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 Convex 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.

  • Developer Tools
  • Connects with a key
  • 19 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 Convex is

Backend-as-a-Service platform with real-time database, serverless functions, and built-in authentication

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

How a run works

One message in, the work done in Convex.

  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 Convex. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Convex 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.

19 tools it already has

What it can do in Convex

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

  • Create deploy keyTool to create a deploy key for use with the Convex CLI. Use when you need to generate credentials for CLI-based development or deployment workflows. The generated key provides adm
  • Create DeploymentTool to create a new deployment for a Convex project. Use when you need to create a development, production, or custom deployment. Specify the deployment type and optional configur
  • Create ProjectTool to create a new project on a Convex team, optionally provisioning a dev or prod deployment. Use when you need to initialize a new Convex project in a team.
  • Delete Custom DomainTool to remove a custom domain from a Convex deployment. Use when you need to delete a previously configured custom domain.
  • Delete DeploymentTool to delete a Convex deployment. Use when you need to permanently remove a deployment and all its data. WARNING: This action will delete all data and files in the deployment and
  • Delete projectDeletes a Convex project and all its deployments permanently. Use when you need to permanently remove a project and all associated data. This operation cannot be undone.
  • Execute Query BatchTool to execute multiple Convex query functions in a single batch request. Use when you need to fetch data from multiple queries efficiently in one API call.
  • Get Deployment DetailsTool to retrieve details about a Convex cloud deployment. Use when you need to get information about a specific deployment including its configuration, region, creation time, and s
  • Get Project by IDTool to retrieve detailed information about a specific Convex project by its ID. Use when you need to fetch project metadata including name, slug, team association, and creation ti
  • Get Project by SlugTool to retrieve a Convex project by its slug within a team. Use when you need to fetch project details using human-readable identifiers instead of numeric IDs.
  • Get Query TimestampTool to get the latest timestamp for queries from Convex deployment. Use when you need to retrieve the current query timestamp from the Convex API.
  • Get token detailsTool to retrieve token details for the authenticated token. Returns the team ID for team tokens or project ID for project tokens. Especially useful after receiving a token from an
  • List Deploy KeysTool to list all deploy keys for a specified Convex deployment. Use when you need to view all authentication tokens that can be used to deploy to this deployment.
  • List deployment classesTool to list available deployment classes for a Convex team. Use when you need to check which deployment classes are available for a specific team.
  • List deployment regionsTool to list available deployment regions for a Convex team. Use when you need to check which regions are available for deploying a team's backend.
  • List DeploymentsTool to list all deployments for a Convex project. Use when you need to see all deployments (production, preview, or local) for a specific project.
  • List Log StreamsTool to list all existing log stream configurations in a deployment. Use when you need to view configured log streaming destinations like Datadog, Webhook, Axiom, or Sentry.
  • List ProjectsTool to list all projects for a specific Convex team. Use when you need to retrieve all projects associated with a team by team ID.
  • Update DeploymentTool to update properties of an existing Convex deployment. Use when you need to modify deployment settings such as dashboard edit confirmation or deployment reference. Only the fi
Access, and who is in charge of it

You stay the boss of your Convex 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 Convex 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 Convex 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 Convex 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 Convex

Can an AI employee really work inside Convex?
Yes. It signs in to your own Convex 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 Convex?
No. Nothing moves and nothing is replaced. Your records stay in Convex, 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 Convex account?
You paste in a key from your own Convex account. It is kept encrypted, and you can withdraw it from inside Convex 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 Convex?
It has 19 ready-made tools in Convex today, among them Create deploy key, Create Deployment and Create Project. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Convex 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 Convex 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 Convex?
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 Convex is written down with what it did and when.