Raspberry Compass

Operations ticketing

Requests come in, get routed, and get resolved. Raspberry Compass is the system behind the small things that keep a building running — the broken latch, the dead monitor, the box of gloves nobody ordered — so none of them live in somebody’s inbox or on a sticky note behind the desk.

Three kinds of request, one queue

Most organizations run these separately, or not at all. Raspberry Compass treats them as the same problem: somebody needs something fixed, and somebody else needs to know about it.

Maintenance

Anything physical — a room, a door, a temperature, a leak. Raised where it happened, routed to whoever handles it, and closed with a record of what was done.

IT & equipment

Hardware that stopped working and software nobody can sign in to, in the same queue as everything else, so nothing falls between two teams who each thought it was the other’s.

Supply

Requests against a catalogue you control, so “we’re out of…” becomes a tracked item with a person attached rather than a message somebody meant to pass on.

The room that keeps breaking, finally visible

Every open request becomes heat on the room it came from. Filter by trade to find the pattern — the tub room that floods, the station where the network drops. This is sample data from a care home, the sector Raspberry Compass was built in; the real map is a plan of your own building, whatever kind you run.

What you get around it

The ticket is the easy part. What makes it usable on a Tuesday evening with one person on shift is everything wrapped around it.

  • Role-based views. Everyone sees their own work, not everyone’s.
  • A full audit trail. Every status change, every reassignment, with a name and a time against it.
  • Floor-plan heatmaps. Where requests actually come from, on a plan of your building.
  • Recurring work. The checks that happen every month, raised on their own.
  • Escalation and nudges. Tickets that go quiet come back, to the right person.
  • Multiple sites. One installation, every site you run, kept properly apart.
  • Analytics. What breaks, where, how often, and how long it takes to close.
  • Built for shared devices. Tablets at a desk, phones in pockets, older machines in offices.

Two ways to run it

The same software either way. The difference is who keeps the server running, and that is a decision about your organization rather than about the product.

Hosted by us

We run it in Canada and you sign in. Your own instance and your own database — not a row in somebody else’s. Updates, backups and monitoring are ours to worry about. Billed monthly or annually.

On your own hardware

Installed on your network, administered by your IT, with nothing leaving the building. An annual licence, or buy it outright and keep running it forever whether or not you ever pay us again.

Handling health information?

Then self‑hosted is the answer, and deliberately so. Care operators have obligations about where resident information lives; the cleanest way to meet them is for it never to leave your site. That is what this product was originally built for.

Priced by the site, never by the head

One price per site, with unlimited staff accounts on every tier. The people who raise the most tickets are usually the ones a per‑seat licence quietly prices out, which is exactly backwards.

  • Unlimited users. Every shift, every department, every casual. No seat maths.
  • All features included. No module that turns out to cost extra once you need it.
  • Hosted: monthly or annual, per site.
  • Self‑hosted: annual per site, or a one‑time perpetual licence.
  • Perpetual means perpetual. Pay once and it keeps running on your hardware, with or without a support plan.
  • No setup fee to talk to us. Tell us how many sites and we will tell you the number.

Want to see it?

Raspberry Compass is built and being readied for its first customers. If you run buildings and you are tired of the sticky notes, we would like to hear what your week actually looks like.