About UtilitySpaces

Why does this product exist?

Because of a problem that shows up the moment anyone tries to put an AI agent on real work. To be useful, an agent has to touch a real system — a store, an inbox, a spreadsheet, a CRM. To touch a real system it needs credentials. And the shortest path to credentials is to hand over yours, which is how a great many agents are currently being run and is a genuinely bad idea: the agent inherits everything you can do, in every application, with no record of which of you did what.

UtilitySpaces is the other path. Every connected application gets its own permission boundary rather than your password. Agents get a role and a set of tools rather than an account. A connector write waits for a person unless an admin has set that connection to run without asking, merges and reviewed work stop at a human approval, and every call and decision is written to a hash-chained audit log that can settle an argument about what took place. The order of those three is the whole design: scope first, gate second, record third.

What is it for?

Teams whose operations already run across several applications, with recurring work that nobody enjoys and nobody wants to get wrong: order triage, inbound enquiry qualification, weekly reporting, the small daily jobs that sit between two systems that do not talk to each other. It assumes you have real systems worth connecting. The product overview walks through what that looks like in practice.

What does this product refuse to do?

• No invented social proof. There are no customer logos, testimonials, star ratings or user counts on this site, because there are no published customers yet. A wall of borrowed logos would be the first lie on an otherwise honest site, and review markup nobody earned is a manual action waiting to happen.
• No dark patterns. No countdown timer that resets on refresh, no fake scarcity, no pre-ticked upsell, no cancellation flow designed to exhaust you. The price list is the actual price, and the demo workspace opens without talking to anyone.
• No selling or mining your data. Workspace content is not sold, not rented, not used to train models and not mined for advertising. The privacy policy states what is collected and why, and the sub-processor list names every third party that can touch it.
• No claiming certifications we do not hold. The security page lists what is in place and what is missing, in the same list, including the gaps a procurement questionnaire would find.

How is it operated and supported?

UtilitySpaces is a managed service. It runs on servers we operate ourselves, with our own database and our own mail delivery rather than a stack of third-party platforms; the short sub-processor list is a consequence of that rather than a marketing line. There is no build you can download and run on your own machines.

Support is email, and it reaches the people who write the code rather than an outsourced desk. We reply to every message within one business day. Support hours are Sunday to Thursday, 09:00–18:00 (UTC+3), and support@utilityspaces.com is the address to use. There is no sales team and nobody will call you.

What are the honest limitations?

They are real and worth pricing in before you buy. There is no third-party security certification — no SOC 2, no ISO 27001 — and no 24-hour on-call rota, so an overnight failure is fixed the next working morning. Two-factor authentication and single sign-on are both available. The security page states each of these plainly rather than burying them.

If one of those is disqualifying for your organisation, the honest answer is that UtilitySpaces cannot meet that requirement today. It is worth saying so on the contact page anyway: knowing which requirement blocked a real team is how the order of the work gets decided.

Where can I see what it actually does?

The product overview walks through the workspace, the agents, the connected applications and the approval gate, with a page per capability. The blog has the longer arguments behind the design choices. If you would rather just ask a question, the contact page reaches a person, and support@utilityspaces.com reaches the same people.