Tickets, assets, patches and security on a single data model — priced by module, built for small IT teams and MSPs who are done juggling five tools.
A helpdesk here, a spreadsheet of assets there, patching by hand, alerts in three inboxes. Every tool has its own login, its own bill, and its own version of the truth.
The ticket lives in one app, the laptop it's about lives in another, and the patch that would fix it lives in a third. You are the integration.
Big suites bundle forty features to justify per-agent pricing that punishes small teams. You use six of them.
When nothing shares a data model, every audit, renewal and incident review starts with an archaeology dig.
Batchster is built module by module on the same core — the asset links to the ticket, the ticket links to the patch job. Start with ticketing, add the rest as they ship.
A service desk your requesters actually use — email-to-ticket, SLAs, portal, knowledge base, CSAT.
Scan the network, inventory every endpoint, and link each device to its tickets and warranty.
See what's missing everywhere, then push updates in controlled batches with reboot windows.
Posture, alerts and response in the same console — isolate an endpoint and the ticket opens itself.
Everything below is working in the Batchster prototype today — not a mockup of a someday product.
Requesters just email support like they always have. Batchster turns it into a numbered ticket, sends a branded auto-reply, and round-robins it to a technician before you've read the subject line.
Every priority carries a resolution target. Countdown chips sit on every ticket, the clock pauses while you wait on the requester, and breaches get flagged before your client flags them for you.
As requesters type, the portal suggests knowledge-base articles that solve it on the spot — every read is a ticket you never triage. And when a ticket closes, a one-tap rating tells you how the team is really doing.
Turn on ticketing today, add patching when you're ready. No forty-feature bundle, no per-agent tax designed for 500-seat enterprises.
The ticket knows which laptop it's about. The laptop knows which patches it's missing. The security alert opens the ticket itself. One truth, zero swivel-chairing.
Batchster is being built in British Columbia by someone who spends his days on FortiGates, M365 tenants and BitLocker screens — every feature earns its place in a real queue first.
Early-access partners get the ticketing module free during beta, a direct line to the builder, and lifetime founding pricing when modules go live.
The ticketing module is in early access: email-to-ticket, SLA timers, a requester portal with knowledge-base deflection, CSAT and live reports. Asset discovery is next; patching and security follow on the same data model.
Free while in beta. After launch, pricing is per module — you pay for what you turn on, not for a suite. Founding partners keep a lifetime discount on everything.
Yes — email-to-ticket is built on Microsoft Graph against a shared mailbox (e.g. itsupport@yourcompany.com), scoped so Batchster can only touch that one mailbox. Google Workspace support is on the roadmap.
CSV import for tickets, contacts and assets is planned for launch. Early-access partners get hands-on help moving over — it's the fastest way for us to learn what migrations really look like.
A working IT administrator in British Columbia, Canada, building the tool he wishes existed — with modern infrastructure (Next.js, Postgres, Microsoft Graph) and an unreasonable number of opinions about ticket queues.