For people who run other companies' IT
Every client kept apart, and an invoice that closes itself
Managed service provider, break-fix shop, IT consultancy: the client record separates each company you serve — tickets, assets, vault, hours and billing.
The stack you pay for today
Each line bills differently — one per technician, another per endpoint, another by volume. That is why nobody can work out what serving a client actually costs.
Today · five subscriptions
- Help desk
- per technician
- Monitoring
- per endpoint
- Remote access
- per session
- Timesheet spreadsheet
- free, and costly
- Invoicing system
- per document
Plus WhatsApp holding it all together, which bills nothing and records nothing.
Here · two lines
- The whole platform
- R$ 89,90 / technician
- RMM add-on
- R$ 29,90 / machine
- White label, if you want it
- R$ 59,90
- Annual discount
- −10% / −15%
- Setup fee
- R$ 0
Above 100 machines, the per-machine price moves to volume negotiation.
What changes when the client is another company
It is the same operation as in-house IT — ticket, SLA, project, hours, machine. What changes is the boundary between one client and the next, and it has to be real.
- The boundary lives in the database, not the screen
- Separation between clients is enforced by Row Level Security in Postgres. A badly written query returns zero rows instead of the neighbouring client's data — which, in an MSP, is the difference between a bug and a breach of contract.
- The portal is yours, not ours
- Your logo, colors and domain on the client portal, for R$ 59,90/month. Whoever opens the ticket sees your brand — and follows it themselves instead of calling to ask where it stands.
- A vault per client, with a record
- Client credentials leave the notepad: a separate vault per account, permissions by role, sharing through expiring links, and every access logged with author and timestamp.
- Hours carry through to billing
- Browser timer, approval before anything becomes an invoice, and invoices assembled from the approved hours. A contract that loses money shows up during the month, not after it.
- The alert arrives with the client already filled in
- Every monitored machine is an asset on a client record. When the alert opens a ticket at 3 am, it is born on the right account with the asset attached — nobody has to work out whose machine it is.