Own It 3.0 is the release where your tools stop being usable only by you. Every tool in the catalog now speaks MCP — the open protocol Claude, ChatGPT agents, n8n and a growing list of AI clients use to operate software — on one endpoint, authenticated with the same revocable API keys 2.0 introduced.
As with 2.0: nothing was taken away, nothing moved behind a paywall, no new subscription. The same one-time purchase you already made.
The agent door, and why it is guarded
Point an AI assistant at POST /mcp with an API key and it can use the tool — list, create, report, record — through the same code paths the screens use. That sentence is the whole design. An agent recording a sale in Vendra runs the same checkout the till runs, so it cannot oversell. An agent approving in Approva faces the same segregation-of-duties guard, so it can never approve its own user's request. Calling the next ticket in Tokora is atomic, so two desks can never call the same person.
Try the Vendra demo ↗Live, on sample data, no sign-up.
Just as deliberate is what agents cannot do. Invora ships no send tool and no delete tool — mail and destruction stay human clicks. Approva ships no PO tool — committing money to a supplier stays a human decision. Waiverly exposes only read tools, because a signature an agent could manufacture would not be worth the pixels it is drawn with. Every tool description states plainly whether it writes.
What else is in the wave
Roles, with invitation links. Viewer / member / admin (named for each product's real jobs), single-use invite links that expire in seven days, a last-admin guard, and deactivated users whose API keys die with them — enforced in the browser, the REST API and over MCP alike.
An append-only audit trail. Who did what, when, from which door — browser, API or agent — on one filterable page with CSV export. Append-only means exactly that: there is no edit route.
Printable PDFs. The documents each tool's paperwork actually requires — invoices, statements, rosters, permits, month-end packs — rendered server-side with no external service involved.
Your logo and your colors. Upload a logo, pick an accent, and the whole app — screens, PDFs, sign-in page — wears it. A buyer-facing install should look like your business, not ours.
Scheduled backups and a guided restore. Backups can now run on a schedule, and restoring one walks you through a dry-run diff first — what would be created, changed and deleted — before you commit. A restore you cannot preview is a gamble, not a safety net.
Optional single sign-on. OIDC against Microsoft Entra, Google Workspace, Keycloak or any standard provider, with break-glass local login preserved. Off by default; your install, your call.
How to upgrade
Replace the files and load any page — the database migrates itself, additively. Your config.php, uploads and data are untouched. If you bought through the store, your download already serves the 3.0 files.
With Slotly shipping its 3.0 on 9 August, the wave now covers the whole catalog — every tool, one upgrade, the same one-time purchase.