@jori answers in Slack, GitHub, Linear, and more
The shared drive your AI works out of.
Tell Jori what needs doing and when. They run the job in the background and keep the results in shared folders, alongside the tables and files your team uses.
Maya Lund09:12
JoriAPP09:12
Hand over the work nobody wants
Weekly summaries, invoice reminders, ticket triage. Describe the work and give Jori the access they need. They run the job on a schedule or when an event triggers it, and save the results in your workspace.
Jobs are just instructions
Describe the job the way you'd brief a person. Choose a schedule, a date, or an event in a connected app. Jori runs the job in the cloud, even when your laptop is closed.
- Write the instructions
- Type @ to add access, / to add a skill, or # to choose a tool.
- Choose what the job can use
- Give each job access to the accounts and tools it needs. Web search is off until you turn it on.
- Keep it in a folder
- The folder limits who can see the job and groups its AI spending with the other work inside.
Work lands where you can find it
Jori can update tables, save files, and keep track of work between runs. You can open and edit the same materials to check or correct the results.
- Tables
- Edit rows, choose column types, and import or export CSV files.
- Stores
- Keep data a job needs between runs, such as what it checked last. Each store holds a JSON document with a structure you define.
- Files
- Open PDFs, images, and notes in the workspace. Files Jori creates are marked so you can see who made them.
See AI spending by folder
Check a folder's usage to see the AI spending for the work inside. Choose a time period, compare jobs and subfolders, or open a run to see its cost.
- By team
- Give each team a folder to see its AI spending in one place.
- By source
- See which jobs and conversations account for the spending.
- Down to the run
- Follow each charge to the run that incurred it.
- No seats, no markup
- One monthly plan for the organization. Additional AI usage is prepaid at the model provider's published rates.
Share it like a drive
Keep work private, share it with people or teams, or open it to your organization. Set access on folders and individual items. Share read-only links with people outside the organization.
- Folders limit access
- An item can be shared with fewer people than its folder, but never more.
- Share with a team
- Group people into teams, then share folders and items with the whole team.
- Choose when links expire
- A share link opens a read-only page without signing in. Set an expiry time or revoke the link whenever you need to.
Everything on the record
Every run records what triggered it, what Jori did, and what it cost. Open the activity log to review the work or stop a run.
- See what happened
- Each run shows the tools used, model calls, token usage, duration, and cost.
- Ask first means ask you
- Set a tool to ask first and Jori asks for approval before using it. Scheduled and event-triggered runs cannot use these tools.
- Stop a run
- Stop a run from the activity log. Its record shows who stopped it.
The same Jori, wherever you work
Mention Jori in Slack, GitHub, or Linear and they answer in the thread. Tables and files they create stay in your Jori workspace, with links in the reply.
Connect the tools your team uses and choose what Jori can do in each.
COP-73Tip-pooling certification
@jori what's left before this ships?
Payroll sync test is flaky on CI#491
@jori can you fix this and open a PR?
Stored in your region
Choose an EU or US workspace. Jori stores your chats, files and workspace records in your chosen region.
- Nothing shared between the two
- Separate applications, databases and file storage in the EU and US.
- What leaves the region
- Page fetching and billing use global services that may process data outside your chosen region.
Start with one recurring job.
Tell us what your team does by hand every week. If Jori is a fit, we'll invite you to a paid pilot and help you set up the first job.