Roadmap

What we are building, what is next, and what we have decided not to build.

Being built now

• Self-service subscription and payment with GST tax invoices, credit notes and self-service cancel.
• A published comparison set against the asset and ITSM tools people evaluate us next to, every claim sourced and dated.
• A documentation site covering the asset import, email setup, the lifecycle and the API.

Next

• Barcode and QR scanning from the phone camera for issue, return and stock-take.
• A guided annual stock-take that produces a signed reconciliation report.
• Custom domain for your help centre.
• Single sign-on with Google Workspace and Microsoft Entra.

Asked for, not yet scheduled

• Depreciation schedules and a finance-grade asset valuation export.
• Purchase orders and goods-receipt notes.
• WhatsApp as an intake channel.
• A customer-managed encryption key.

Decided against, for now

A plugin marketplace: it would mean running other people's code next to employee records, which is exactly the dependency surface we have spent effort removing.

On-premise licensing: we would rather run one platform well than support installations we cannot see. If a compliance requirement genuinely needs it, write to us and we will talk.

Tell us what you need

This list is shaped by what customers ask for. A specific request from a real user beats our own guess almost every time — if something here would change your mind about the product, say so.

How this list is decided

Roughly in this order: things that are broken, things that block somebody from using what we already built, things several customers have asked for, and then things we think are right. A specific request from a real user with a real problem beats an internal idea almost every time, which is why the middle two categories move fastest.

We do not publish dates. A date on a public roadmap is a promise made before the work is understood, and the honest version is an order rather than a calendar. What we will do is tell you when something you asked for ships.

Why some obvious things are missing

A few capabilities that appear on every competitor grid are deliberately absent, because adding them would mean loading third-party code next to employee records or moving that data out of India. Where that is the trade, we would rather not have the feature — and say so here — than have it and quietly weaken the promise the rest of the product is built on.