About us

A small product company in India, building the IT operations system we wanted to use.

Why this exists

This product started because of an actual IT department, not a market study. The service desk was a shared mailbox, the asset register was a spreadsheet one person maintained, and the two never agreed. Every audit began with two hours of reconciliation, and every exit ended with somebody chasing a laptop by email.

The tools we evaluated solved one half or the other. The ones that did both were priced per end user in dollars and hosted abroad, which turned a software decision into a budget argument and a compliance conversation at the same time.

So we built one, and used it in production before we ever sold it. That is why the unglamorous parts — the state machine that refuses a nonsensical move, the serial uniqueness rule, the audit log — are the parts that work best.

How we are funded

By customers. No venture funding, no investor growth target, and no pressure to inflate a number before a round. We grow slowly — and we are not going to be acquired and shut down next year, or raise prices three times to hit somebody else's plan.

What we will not do

• Sell, rent or mine your data — including the employee records this product necessarily holds.
• Put an advertising or analytics script on a page where your staff raise a ticket.
• Make you email someone to cancel, or bury the cancel button behind a retention flow.
• Claim a certification we do not hold, or a customer count we cannot evidence.
• Block a device return, an exit or a data export because of a billing limit.

How we build

Server-rendered pages, no JavaScript framework and no build step. That keeps pages fast on an average Indian mobile connection, keeps the dependency surface close to zero, and means no script, font or tracker your staff loads comes from a third party. The pages are delivered through our hosting provider's CDN, which is listed on our sub-processors page.

We ship small and often, and every release is written up in plain English on the changelog — including the fixes that were our own fault.

Built for IT, and only for IT

SupportCentral is for the people who run an IT estate: the service desk, the asset register, joiners and leavers, licences and the security software. We have deliberately not stretched it into a desk for every department, because what makes it useful to IT — the device on the ticket, the exit that will not close while a laptop is still out — is exactly what a general-purpose tool leaves out.

It is built by Support IT Ventures.

Where you can reach us

Who runs this site, and which inbox to use for what, is on the contact page. If you need to escalate past support, the grievance page gives the grievance inbox and the timelines we hold ourselves to under Indian law.

How we support people

Support is by email, answered by the people who build the product. There is no first-line script and no tier to escalate through, which is the main advantage of being small: the person replying can usually fix the thing rather than log it.

We publish response times on the pricing page and we mean them. If we are going to miss one, we will tell you before it is missed rather than after.

What you can hold us to

• Your data is exportable in full, at any time, in any account state, at no charge.
• Cancellation is self-service and takes two clicks.
• Thirty days notice before a price change, and before a sub-processor is added.
• An honest changelog, including the fixes that were our own mistakes.
• No certification claimed that we do not hold, and no customer count we cannot evidence.
• A reply from a person who can actually change the thing you are writing about.

Where we are going

The plan is unglamorous: keep the product fast, keep the dependency surface near zero, keep the data in India, and add the things customers actually ask for rather than the things that look good in a feature grid. The roadmap says what that means this quarter, including what we have decided not to build.