What itbudgit is, what it isn't, and what happens to your data.
A reconciliation and planning ledger for IT budgets. It holds your budget, your actual spend and your contract obligations in one place and lines them up, so the gaps between what you planned, what you were billed and what you're committed to are visible instead of buried across three files.
Yes. The demo link opens the actual application, pre-loaded with a fictional group called Helios Group. Three subsidiaries, real contract structures, renewals and licence positions. You're clicking through the genuine tool, not a video or a mock-up.
Nowhere but your own machine. The demo runs entirely in your browser. Nothing you type is sent to a server. It does save to this browser's local storage, so your changes are still there when you come back; clearing your browser data deletes them, and they are not backed up anywhere. It's a safe place to explore and a bad place to keep the only copy of anything. Private, backed-up accounts arrive with the hosted product.
The hosted version (your own account, saved data, sign-in and backups) is built and running. You can sign up and start today. There is no free tier and no trial: you pick a plan on the way in, and a workspace with no plan is readable and exportable but not editable, so nothing is ever taken away from you, and nothing is dangled either. If you want to run your real 2026 or 2027 budget on itbudgit, get in touch and we'll talk about being an early customer.
Both, and you switch which one you are reading. As invoiced shows a cost when the money is billed, that is the stream your postings and transactions live in, and the one you reconcile against a bank statement. Accrued shows it when it is economically consumed. The stream finance reviews. A contract billed quarterly is four lumps in one view and twelve even months in the other, and the year-end total is identical.
Two things keep it honest. The choice of whether a cost is recognised across its term is made per contract, not by whoever is looking at the screen. Switching the view never changes that decision and never changes your data. And the accrued figures are derived when you look at them, from the same stored cents, rather than kept as a second set of numbers. There is nothing to reconcile between the two views because there is only one set of numbers underneath.
It is one setting for the whole workspace, deliberately: if two screens could sit on different bases, a figure would change meaning as you navigated and you would have no way to tell. You can also set which basis a workspace opens in, so the people who live in one of them are not switching every morning.
A flat annual fee in one of three tiers, not per seat, and not a percentage of your spend. Viewers are always unlimited, because the people who need to look at the numbers shouldn't cost you a licence. Ledger (€129/mo) is the reconciliation core: budget, actuals, contracts, renewals and indexation. Portfolio (€249/mo) adds the showback layer. Teams, allocation keys, projects and licence positions. Group (€549/mo) adds multiple legal entities and the two-role vendor model. Full comparison on the pricing section.
Answer one question: who has to see what this costs? If it's just you reconciling a budget against contracts, Ledger is the whole job. If you have to tell four teams what their share is, and defend the split, that's Portfolio, and the allocation keys are the reason. If you're consolidating more than one legal entity, or buying the same technology through several resellers, that's Group.
Those platforms are strong at discovering usage. Scanning your SaaS estate, pulling telemetry, integrating with your ERP. They're powerful and priced accordingly. itbudgit goes the other way: no discovery, no agents, no integration project. It's strong where they're weak. Treating the contracted entitlement as a structured fact tied to term, entity, cost centre and renewal. Different job, an order of magnitude simpler to adopt, and priced for a single team's budget rather than a board decision.
The company you pay and the company whose technology you run are often different. A reseller versus the vendor behind it. They fail independently: the reseller's commercial terms are one risk, the vendor's roadmap is another. itbudgit tracks both roles separately, so you can roll up your total exposure to, say, Microsoft across every reseller and legal entity. Something a flat supplier column can't do.
No migration project. itbudgit reads the workbook you already keep (budget lines, actuals, contract terms) so you bring what you have rather than re-keying it into a new system. The importer tells you what it changed rather than quietly adjusting figures: if a posting is dropped or a cell reads as empty instead of zero, it says so and names both numbers.
A full Excel workbook, any time, that re-imports cleanly. That's the same round-trip the importer uses, so it isn't a lossy "report export". If you ever stop paying, the workspace becomes read-only (not deleted, not hidden) and exporting still works. Your numbers are never held hostage.
Not yet, not a published one. The hosted product already talks to its own server over HTTP, but that isn't documented, versioned or supported, and selling it as an API would be dishonest: a published interface is a promise not to break your integration. It's on the roadmap, and if feeding a BI tool or an ERP is what would make this work for you, tell us, that is genuinely how the order gets decided. Meanwhile nothing locks your data in: the Excel round-trip works today, with no API at all.
Closer than anything else on the roadmap, but not proven, so it is not being sold yet. Here is exactly where it stands.
itbudgit deliberately does not implement sign-in itself: identity is delegated to a provider (Clerk or WorkOS), which is where enterprise SSO against Okta, Entra ID or Google is configured. What itbudgit builds is the half that cannot be delegated. Verifying that the token in front of it was genuinely issued by that provider, and mapping your organisation to your workspace. That half is built and adversarially tested: unsigned tokens, tampered payloads, untrusted signing keys, wrong issuer or audience, expired tokens and organisations it has never heard of are all refused, and a role always comes from the signed token rather than from anything the browser sends.
A live provider is now connected and that whole path runs end to end on the hosted build. A real sign-in, a real token, the right workspace. What is left is the enterprise directory connection: pointing that provider at your Okta, Entra ID or Google tenant and proving that specific path. Until that is done it stays a roadmap item rather than a feature, because "it should work" is not something you should have to take on trust. If SSO is a requirement for you, tell us: it is the item most likely to move first, and being early is what decides that.
Two answers, and the difference matters. Not yet: multiple currencies with dated FX (a workspace holds one today, and switching re-labels rather than converts), depreciation schedules, and a published API. Each of those is on the roadmap with an honest status against it, and the order is set by what customers ask for. Single sign-on is further along than the rest. See below.
Built since this list was written, and left on the roadmap saying so rather than quietly removed: two people can enter data at the same time on the hosted build, with disjoint edits merging and a same-cell clash raised as a named conflict for a person to settle; and an admin can put an earlier version back from Admin · Data, out of a twelve-month trail of every accepted change. Both still have a half outstanding, and the roadmap names which.
What it will never do is allocate costs through a tower model, publish internal rate cards, issue chargeback invoices or run discovery agents on your endpoints. Those aren't gaps and they aren't coming. They're the other product, and it already exists.
itbudgit is built and run by a solo developer with a background in exactly this problem. See the about page. Being small is the point: you get a tool with a clear opinion, not a committee's compromise. It also means support is a person rather than a 24/7 desk, and there's no uptime SLA. Worth knowing before you buy, not after.
Open the demo, switch between the reconciliation, renewal calendar and licence positions, and see whether it fits the way you actually work.
Open the live demo