One record of what you run, what it costs and what is changing it.

Shadow AI and AI agents

Which AI tools and agents are in use, who owns them and what data can they reach? Find the ones nobody registered, tier them by risk and give your board a current answer.

See shadow AI discovery →

Shadow IT and SaaS sprawl

See every application your people use and pay for, including the ones bought on a card, and decide which to keep, merge or retire.

See the first report →

Renewals and wasted licences

Never miss a notice date again, and get unused seats back into a pool before the renewal, with finance signing each saving once.

See the renewal clock →

A portfolio that keeps itself current

A capability map and a position on every application, filled from live data so it stops going stale, with reviews sized to the risk.

See the capability map →

One view of change

Requests, renewals and projects on one record, with status drawn from the delivery tool and benefits measured from real spend.

See request to delivery →

Evidence on request

Access reviews, leaver checks and a log of who approved what, ready for an auditor without a scramble. See a [regulated approval workflow we built](case-compliance-vendor-approval.html).

See the smaller features →

Shadow AI and shadow IT, found in days

Connect read-only to the systems you already run. Within about two weeks you see the AI tools, agents and applications nobody registered, with spend, unused seats and renewals alongside.

Records that keep themselves current

The portfolio fills from identity, finance, card and contract feeds. People are asked only for judgement: who owns this, how critical it is and what should happen next.

One answer for the CIO, the architect, the PMO and finance

Each person opens on the screen that answers their question, from the same records. The capability map, the renewal board, the project funnel and the savings ledger never disagree. The idea behind it is operational intelligence.

Decisions that reach the work

A board decision becomes a record that gates, renewals and project plans read. A retirement counts as a saving only when the spend has actually stopped.

Discover

Find what the company runs and pays for, including applications and AI agents nobody registered.

Decide

Route every request by size and risk, set an architecture position and make the renewal decision with the facts in front of you.

Change

Carry the decision through a request, a renewal or a project, with owners, gates and a roadmap.

Prove

Show that the money moved. Finance signs each saving once, and every figure links back to its source.

SaaS management core

For the CIO, head of IT operations, procurement and finance. Discovery, spend and contract matching, the front door, fulfilment and seat pool, renewals, licence reclamation, offboarding, access reviews, the savings ledger and the IT pack. It also includes a read API, a read-only MCP server and continuous export to a bucket you own.

Architecture tier

For the head of architecture. Capability mapping, TIME assessment, technology risk and standards, tiered architecture reviews, the decision log, derived lifecycle, observed interfaces, the rationalisation workbench, the roadmap and the architecture pack.

Portfolio tier

For the PMO lead and head of IT portfolio. Demand triage, business cases, prioritisation, stage gates, derived status, RAID, benefit lines, weighted objectives, the portfolio pack, and import from spreadsheets and legacy project plans.

Shadow app and risk triage

On the first sighting of an unapproved app, the product scores its risk, checks for overlap and asks the first user what it is for and what data goes in. A free, low-risk app with five users or fewer and no overlap is marked Allowed. Overlap triggers an offer of the approved app. Blocking is advisory, and revoking access is always a ticket. This is the same discovery that catches vibe-coded apps built outside IT.

Spend matching and contract capture

Card descriptors and invoices are cleaned and matched to vendors, invoices are split by line, and currency is converted at the transaction-date rate. Contract terms are extracted by AI and stay Inferred until a named person confirms them. The product never reads full card numbers and never makes payments.

Ownership and freshness chase

Each application has a business, technical and budget owner. The product suggests an owner with the reason, such as "212 active users in Marketing, renews 14 March", and asks Accept, Not me or Ask a question. Leavers' apps move to their manager the same day, and nobody gets more than one question or nudge per app a week.

Technology risk and standards

For custom, hosted and desktop software, the product joins versions to end-of-support dates and to your adopt, trial, contain and retire standards. The technical owner picks Plan upgrade, Accept risk until a date or Already handled. Accepted risk expires and re-triggers.

Observed interfaces

App-to-app OAuth grants, API connections and MCP links seen by the feeds are recorded as interfaces, so the impact of retiring an application shows what depends on it.

Seat pool, access and purchase

Access requests pick a tier, role and duration and follow the policy's approval chain. A pooled seat is used first, and the seat expires by ticket. Use is checked after 30 days. Purchases go in parallel to the budget owner, security, the architect and procurement, and the signed contract creates the vendor, application and renewal. Privileged roles never self-serve.

Demand triage

A daily digest proposes a route for each demand: fast track, one-screen case, full case, merge or reject with a reason. The demand manager accepts or changes it in one click. Findings and renewals never create initiatives on their own.

Business case

The product drafts options, cost lines and benefit lines, each bound to a measure such as "matched spend reaches zero". The project manager writes up to 300 words and a sponsor confirms. Above the board threshold, finance reviews and the portfolio board approves.

Prioritisation and scoring

Initiatives are scored for strategic fit, financial return, cost removed, risk reduction and delivery confidence, ranked, and a funding line is drawn. Manual moves need a visible reason, and the board approves the funded list. Estimated effort is totalled by team per quarter.

Rationalisation and retirement proposals

Candidates are ranked by saving multiplied by confidence, with a target app. The impact view shows users, interfaces, data to export and the last safe notice day. On approval it raises a demand carrying the evidence, fast-tracked if small.

Stage gates and change control

Each gate pack marks every item evidenced, attested or missing. At the build gate the product checks that the review passed with no open conditions, that security and data protection are signed off and that a baseline exists. Variance opens a pre-filled change request, and impact changes reopen architecture review.

Derived status

Schedule, cost, scope, adoption, risk and overdue conditions each get a rating from the data. The project manager gets a card to confirm, edit or override with a reason. After Friday noon an unconfirmed status is published marked "not confirmed by PM". Adoption turns red only on Likely or Confirmed usage.

Roadmap, risks and conflicts

The roadmap is derived from each initiative's impacts and milestones. The product detects conflicts such as a retirement after a notice date, a capability left with no Invest app, or two initiatives on one app in a quarter, and posts each to the risk log as a suggestion with evidence.

Offboarding

For each leaver the product computes their footprint, checks identity deactivation, raises one ticket per non-SSO account, returns licences to the pool and proposes ownership transfer to the manager. It also flags agents, keys and card subscriptions under the leaver's identity. It deactivates and never deletes, and a legal hold stops destructive steps.

Access reviews

A campaign recommends keep or revoke with a reason: leaver, unused for 90 days, policy deviation or moved. Reviewers act from a chat or email card without logging in. Leaver revocations are accepted automatically, privileged access needs a second reviewer, and there is no approve-all on it. The campaign closes with an evidence pack for auditors.

Close and retirement confirmation

For each retired app the product checks zero assignments, no sign-ins for 30 days, unassigned licences, evidence of non-renewal and two billing cycles without spend. Nobody sets Retired by hand. The owner attests data archiving and retention, and benefits are handed over with 3, 6 and 12-month reviews.

Packs for boards and reviews

The IT pack covers spend, savings, renewals, shadow AI and coverage. The architecture pack and the portfolio pack follow with their tiers. Each opens with the decisions needed, links every figure to evidence and carries an AI-drafted narrative labelled a draft until the author releases it. They share as a page without a login, with PDF and slide exports.

Read API, MCP server and continuous export

A read API and a read-only MCP server answer questions over your data, and any proposal they make needs a person to approve it. The full dataset exports continuously to a bucket you own, with a documented schema.

Spreadsheet and legacy project import

A one-off upload with column mapping brings in project registers, project plans and spreadsheets, so the portfolio starts with history. Imported rows are marked as imported.

Browser, device and AI-vendor feeds

After the first value report you can add a browser extension, device management and AI vendor usage reports. The product shows a scope manifest for each, and an aggregate-only mode and a works council pack are available for Europe.

Team-level capacity on the prioritisation board

Capacity by team and quarter, with no named people, so the funding line reflects what teams can deliver.

Cloud account and code-host feeds

Technology components for custom software are read from cloud accounts and code hosts, so the standards and obsolescence views stay current without manual entry.

More agent platforms and connectors

Discovery for further agent and automation platforms, more procurement connectors, a planning-tool connector for status and a ticketing connector for incidents.

Access fulfilment by group add

Where pilots ask for it and security teams accept it, access can be granted by adding a person to an allow-listed group instead of by ticket.

Birthright access, joiners and movers

Access that follows a person's role when they join or move, starting with the ten applications that hold the most seats.

App-level provisioning and revocation

Provisioning and deprovisioning inside applications, and approved revocation of OAuth grants and API keys.

More status and planning connectors

Status from further work-management tools, and read and write-back with financial planning tools.

Price benchmarks and custom dashboards

Opt-in, anonymised price benchmarks across customers, and a dashboard builder for views we have not thought of.

Sovereign deployment in your own estate

Run Arithim Estate inside your own cloud or data centre as an independent application. AI features use endpoints you control: your own GPU clusters, or models through your AWS Bedrock or Microsoft Foundry account, so the AI calls stay within the boundary you set.

Your own workflows

Build your own workflows on the same records, with the same guardrails: review-only first, undo, and an exportable log. The ready-made workflows we ship stay as starting points.

Your own data model

Add your own object types, fields and relationships, so the product can hold what is specific to your organisation. The standard model stays as the default.

Diagrams from your records and from code

Architecture, process and value stream diagrams generated from your records and from code, the way coding assistants draw them today, and kept in step with the data. It works with the diagramming, scheduling and task tools you already use through their APIs, instead of replacing them.

Identity provider

Microsoft Entra ID, Okta, Google Workspace, JumpCloud and OneLogin. Read-only at first. Removal from allow-listed licence groups is opt-in under the second consent.

Microsoft 365 and Google Workspace

Licences, usage reports, OAuth grants and Copilot or Gemini usage, through the same read-only consent.

HR system

Workday, SuccessFactors, BambooHR, HiBob, Personio, UKG and Rippling. Named fields only. No salary, address or protected characteristics. Required before reclamation goes live.

Finance and ERP

NetSuite, Oracle Fusion, Dynamics 365, Sage Intacct and Xero, by read-only role or saved report, with file export accepted and 24 months of backfill.

Cards and expenses

Amex, Ramp, Brex, Navan, Expensify, Pleo, Spendesk and Payhawk, filtered to software merchants, with a CSV fallback. Card numbers are dropped.

Contracts

Bulk upload from day one, then a connector to one named SharePoint or Drive folder, or to Box, DocuSign or a contract platform.

Chat and email

Slack and Microsoft Teams for the front door and every card, with no channel history read. A forwarding address takes request and invoice mailboxes without mailbox access.

Ticketing

Jira Service Management, Zendesk and other service desks, through an integration user limited to one queue.

Delivery tools

Jira Cloud and Azure DevOps. Read work items and, if you switch it on, create epics in one project. Fields only.

Vendor admin APIs

Read-only admin tokens for Microsoft 365, Slack, Zoom, Atlassian, Salesforce, Adobe, GitHub, Miro, Figma and DocuSign. Your ten biggest by spend first.

Devices, browsers and network security

Intune and Jamf, a browser extension for Chrome, Edge and Firefox, and summaries from Netskope, Zscaler, Defender for Cloud Apps and Cloudflare. All optional.

AI vendor admin APIs

OpenAI, Anthropic, GitHub Copilot, Cursor and Copilot Studio usage, cost, seat and agent listings. Never prompts or outputs.

Your own bucket, and your sign-in

Write-only export to your S3, Azure Blob or Google Cloud Storage bucket, and SAML or OIDC sign-in with SCIM from your identity provider.

Connect

You sign the first consent. Identity, Microsoft 365 or Google, a finance export, the card feed, chat, a ticket queue and our sign-in are connected, and contracts are uploaded. You see a connector board with freshness for each source and an inventory filling within hours.

Reconcile

Our onboarding lead works the merge queue with you and connects your ten biggest vendor accounts. You see the first reconciled inventory with confidence on each field and a list of exceptions.

First value report

Spend by application and cost centre, unused seats, shadow IT and shadow AI, renewals by notice date, suggested owners and a draft capability map. The project funnel already shows renewal demands from the clock.

Second consent

Offered on the strength of the report: browser extension, device management and AI vendor reports, each with a scope manifest, and a works council pack where one is needed.

Front door live

The lead architect confirms the starter map for the top 50 applications in an afternoon. The front door goes live with the capability check and the seat pool, and reclamation rules run in review-only mode. Owner coverage passes 60%.

Reviews and demand

Tiered architecture reviews and demand triage go live, and you see the first derived project status with the project manager's override beside it.

TIME and first release of seats

TIME proposals appear with their evidence, the first access review runs on audit-scope apps and reclamation goes live where the HR system is connected.

First signed saving

The first renewal is decided with an architecture position, finance signs the first saving and the first portfolio pack goes out with every figure linked to its source.

Matching names and spend

Decides only when it is very sure, and suggests otherwise. Every merge can be split.

Reading contracts

Drafts the dates, notice period, value and terms. A named person confirms them before any clock uses them.

Mapping capabilities and TIME

Suggests links and positions, marked Inferred. Owners and the architect confirm the ones that matter.

Review packs, business cases and status

Drafts options, cases and up to 120 words of weekly status. The architect, the project manager or the sponsor decides.

Access review recommendations

Suggests keep or revoke with a reason, and accepts leaver revocations. A reviewer decides the rest.

The MCP server and packs

Answers questions over your data and drafts the narrative of a pack. A person approves any proposal and releases any pack.

Two consents, not one

The first covers read-only access to your systems of record, plus messages, tickets and, if you choose, epics. The second follows your first report and covers the browser extension, device management, AI vendor reports and opt-in group removal after 30 days in review-only mode.

What we never ask for

Mailbox or calendar content, chat history, salary or protected characteristics, prompts or outputs from AI tools, full card numbers, write access to finance, ERP or HR systems, passwords, or network scanners on your estate.

Guardrails on every write

30 days review-only for a new rule, allow-listed apps and groups, deactivate and never delete, capped batches, exemptions, one-click undo for 14 days, a kill switch per rule and an exportable log of who approved what.

Your region, your retention

Tenant data stays in its region: the EU and the US at launch, with the UK and Australia on request. Raw usage events are kept for 90 days and daily roll-ups for 25 months.

Leaving is designed in

Continuous export of the full dataset to a bucket you own, a documented schema, a read API and a contractual wind-down of at least 90 days.

Security paperwork

A completed CAIQ and SIG Lite, a data processing agreement with standard contractual clauses, a sub-processor list and a penetration test summary. SOC 2 Type I is planned for launch, with Type II and ISO 27001 within twelve months.

CIO

A capability heatmap with lenses for spend, TIME mix, risk and overlap, a feed of what changed this week and the decisions due at the next board.

Enterprise architect

The capability map and a queue of reviews, low-confidence mappings, contested TIME proposals and expiring exceptions, each with one-click accept.

PMO lead

A funnel from request to realised benefit with value at every stage, an exceptions inbox, the prioritisation board and the pack builder.

Project manager

One scroll: derived status with evidence, milestones, risks, the gate checklist, budget against actuals, the applications in scope and the benefits.

IT and SaaS operations

A decisions inbox sorted by money at stake and deadline: renewals, shadow apps, reclaim batches, ownerless apps with spend and connector failures. See a connected reporting layer we built.

Procurement and finance

The renewal board by notice month, the matching queue, renewal briefs and negotiation packs, and the savings ledger with sign-off cards.

Budget owner

"My money": the apps, spend, renewals, initiatives and benefits for their cost centres, readable on a phone.

Anyone in Slack or Teams

No screen at all. The app answers "I need a tool for X", shows what they already have and carries every card for requests, owner confirmations and reviews.