Built to be checked.

Choose which accounts Jori can use and what they can do. Review their actions and costs in each run's record.

Every tool has a mode

Choose what Jori can do in each connected account. Set tools to Allowed, Blocked, or Ask first.

You can allow Jori to read emails and draft replies while requiring approval to send them. Change tool permissions in the console. Changes take effect on the next run.

Replying in the thread that asked stays on, so Jori can always report back. Everything else is yours to set.

Permissionsa few of the modes you set

Search threads

Search your Gmail threads.

Allowed

Create draft

Save a Gmail draft without sending.

Allowed

Send email

Send a new email from your Gmail account.

Ask first

Create calendar event

Add an event to your Google Calendar.

Allowed

Create pull request

Create a GitHub pull request.

Ask first

Search web

Search the public web.

Blocked

Ask first means ask you

Set a tool to ask first and Jori waits for your approval before using it.

Approve a request in the console, or reply with its code in the thread. If you deny the request or let it expire, Jori does not carry out the action or retry it on their own.

Approval requested#eng on Slack

Comment on the certification issue

COP-73 · Tip-pooling certification
Asking Jonas which two signatures are missing

Review the record of each run

See what Jori read, did, and asked for approval to do, with timestamps for each step.

Each record shows what triggered the run, the tools it used, what it produced, and which folder its spending belongs to. If Jori splits work into subtasks, each links back to the original run.

Jori records each step as the run happens.

Acts as you, never past you

Jori works with the accounts you connect, with the access you grant. Nothing else.

Your accounts, as you: Every action goes through an OAuth grant you approved, integration by integration. Revoke a grant and the access ends with it.
Your context, or the organization's: Work you keep to yourself runs with your integrations. Work shared past you runs with the organization's, never your own.
Members only, on every surface: Only members of your organization can ask Jori for work, steer a run, or approve an action, in Slack, GitHub, and Linear alike. A mention from anyone else, in a shared channel or a public repository, starts nothing and gets no reply.
Subtasks inherit less, never more: Jori can split a job into subtasks. A subtask can never hold access its parent lacks.

Who sees what

Only you, specific people, specific teams, or everyone in the organization. Set it on a folder or an item, and the tree enforces it.

The folder is the ceiling: Nothing inside a folder reaches further than the folder does. Sharing a table wider than its folder changes nothing until the folder allows it.
Links carry their own secret: A share link opens a read-only page. Its secret rides in the URL fragment, it expires on a clock you choose, and you can revoke it any time.

Some things are structural

Not settings, and not promises. The way Jori is built.

Unattended runs can't use ask-first tools: Scheduled and event runs never touch a tool you've gated. Anything that needs your sign-off waits for a run with you in it.
The web is off until you turn it on: Web search and fetch are granted per job, never assumed.
What Jori reads is evidence, not instructions: Text inside emails, pages, and tickets can't redirect Jori, grant permission, or change the task. Only you can.

Where your data goes, and doesn't

Short list, plain words.

Stored in your region: Your workspace data, web searches, and code execution stay in the EU or US region you choose. Page fetching and billing use global services.
Subprocessors: Convex Stores workspace data and sessions.
Cloudflare Stores files.
turbopuffer Indexes content for search.
Vercel Hosts and serves the application.
Blaxel Runs sandboxed code.
Bird Sends Jori's email.
Parallel Runs web searches and fetches pages.
OpenRouter Routes model calls to providers.
Google Cloud Generates images from prompts.
Polar Sells Jori and handles payments and tax.
PostHog Measures usage, if you opt in.
Zoho Hosts the support mailbox.
Never used for training: Not by us, and not by the model providers Jori routes to.
GDPR: Built to comply with GDPR. The data processing agreement is part of the terms, so it applies from day one.
Audits: Independent security audits are planned. We'll publish the results when they're done.
Open source: Jori is open source under the AGPL. Read the code, prompts, and skills on GitHub, including how permissions and sandboxing work. The cloud runs the same code.

Start with one recurring job.

Tell us which job you'd like Jori to take on. If it's a fit for a paid pilot, we'll help you set it up and choose the access it needs.