Runwork
All Use Cases

The AI your company runs

Every team picked a different AI tool and nobody told you

What is connected to your workspace is registered as people connect it, and every important action is written down. You open a list instead of sending a survey.

Powered By

Audit Logs Permissions
Oversight
MCP Servers
Integrations Workspaces

The Challenge

  • Somebody asks which AI tools can reach customer data, and the honest answer is that you would have to go and find out
  • Engineering is fine. The risk is in the departments that never told anyone what they connected
  • Standardising on one vendor is a bet on which product is best in two years, and nobody knows
  • The useful automations run on individual laptops, so they are invisible to you and they stop when the laptop shuts
  • A security questionnaire arrives and half the answers are somebody's recollection

The Runwork Solution

  • The AI tools, integrations and MCP servers connected to the workspace are registered as people connect them, so the inventory exists without anyone maintaining it
  • Every important action is written to a record that is added to and not edited afterwards, and you can search it by person, action or date
  • Access is decided per resource rather than per person: people, the groups they belong to and their department on one side, apps, data, integrations and workflows on the other
  • People keep the AI tool they already chose, and what they build is stored in the workspace rather than inside any one product
  • What is running is visible to any member of the workspace, not only to whoever is senior enough to be sent a report

What your team gets

The question you can answer in a minute

Which AI tools reach our customer data. That is a list you open, rather than an email thread and a week of asking around the departments.

The tool nobody told you about

Somebody in marketing connected something in March. It was registered when they connected it, so it is in the inventory whether or not it was ever mentioned.

Evidence that was not assembled for the occasion

When a customer's security team asks how you would know if something happened, the record already exists. Nothing was written up in the week before the review.

A decision you do not have to make

You never have to pick one AI vendor for the whole company. What people build sits in the workspace, so a team changing tools is their choice rather than your migration.

Roles you can actually change

Owner, admin, editor or viewer, visible on the member list and changeable by somebody with the right role. The change is written into the record like anything else.

Where the controls stop

Single sign-on is not here yet, and it is the one gap on this page. Access itself is as fine-grained as you need: per app, per integration, per set of records, for a person or a group or a whole department.

A Day in the Life

9:00 AM. The question from the board. Which AI tools can reach customer data? You open the list of connected integrations and MCP servers rather than starting a week of asking around. The inventory exists because people connected things, not because somebody maintains a spreadsheet.

10:30 AM. Something you did not authorise, and did not need to. A team connected a tool you have never used. It is registered, it is visible, and the person who connected it is on the entry. That is a conversation rather than a discovery.

12:00 PM. A record changed and nobody remembers. The audit log says who, when, and what the value was before. You close the question in a minute instead of a meeting.

2:00 PM. A vendor changes its pricing. Your teams read it as news about one tool. Nothing the company has built lives inside that product, so the question is whether anyone wants to move rather than what it would cost to.

4:00 PM. The security questionnaire. You are not writing anything new. The evidence they ask about has been accumulating since the day the workspace was created, and the log is added to rather than edited.

5:30 PM. Nothing was reconstructed today. Every answer you gave came out of something already written down. That is the whole difference, and it is why the estate stops being a thing you survey and starts being a thing you read.

Frequently Asked Questions

Do you support single sign-on?
Not today. It is on the roadmap, and we would rather say so on the page where you are looking for it than let a governance argument imply an authentication feature we do not have yet. What ships now is fine-grained access control, set per resource for a person, a group or a department, and every access change written into the record.
How do we control who can reach what?
Through a grid rather than a job title. On one side are the people, the groups they belong to and their departments. On the other is everything in the workspace they might reach: apps, records, connected integrations, workflows, files. You decide what each side may do with the other, so a contractor opens one app and nothing near it, and finance data stays inside finance. Roles are still there as sensible starting points, so nobody fills in a grid on their first day, and every change to any of it is written into the record.
What is actually recorded?
Important actions: creates, updates and deletes on your data, team and permission changes, authentication events, API calls and automation runs, each with who did it, when, and the previous value. Ordinary reading is not recorded, so nothing is written when somebody opens a record. Some read-side actions are recorded deliberately, including exporting your data or the log itself.
Do we have to standardise on one AI tool?
No, and we would argue against it. 60+ AI tools are in the registry, connecting either over MCP or through skills synced by the CLI. What your teams build is kept in the workspace rather than inside any one product, so a team moving to a different tool is their decision rather than your migration project.
Who can see what is running?
Any member of the workspace. The workflows, scheduled work, endpoints and agents that are running are not behind an admin screen, which is deliberate: visibility that depends on somebody senior remembering to circulate a report is not visibility. You see more than most people because of your role, not because the list is yours.

Related Use Cases

What AI Does Any AI Tool Work That Runs

Start keeping what your team figures out.

Start a 14-day free trial. No credit card required.

Start Free Trial Explore More Use Cases