The ticket, the contract and the machine in one place
One platform for people who run IT. Service desk with SLAs, projects, timesheets and billing — and, behind the same login, monitoring for the machines you manage.
No card · 14 days free · data hosted in Brazil
TicketsMy open ticketsTier 1 queueDue todayWaiting on client18 open · 2 past due
| Ticket | Client | Asset | Priority | Assignee | Response due in |
|---|---|---|---|---|---|
| Disk at 94% on SRV-BKP-02#4820 · opened by an alert | Vale Norte Clinic | SRV-BKP-02 | Critical | Ana P. | 27 min |
| Billing office printer offline#4819 · by email | Kron Metalworks | — | High | Bruno M. | 2 h 10 |
| Onboarding · 3 new workstations#4817 · via the portal | Bandeira Studio | 3 ativos | Normal | Ana P. | 1 d 4 h |
| Preventive maintenance · September#4805 · recurring | Vale Norte Clinic | — | Low | Bruno M. | paused |
From a full disk at 3:14 am to a line on the invoice
In the way you work today, that same journey crosses five tools and three people. Here it is one product — and the data is never retyped at any stop.
03:14:22
Agent The machine reports
94%60-second sample on SRV-BKP-02. Third reading in a row above 90%.
Today: your monitoring tool
03:14:22
Critical The rule fires
disk > 90% for 15 min
With a cooldown, so it does not reopen if the volume fluctuates.
Today: someone reading the email
03:14:23
Ticket #4820 The ticket is born
Response SLA: 27 min
Client and asset already attached, with nobody typing them.
Today: your help desk, typed by hand
09:02
Approved The hours are logged
1 h 20 · technician Ana P.
Browser timer, approved before it can become an invoice.
Today: your timesheet spreadsheet
09/30
Invoice It becomes a billable line
#4820 · 1 h 20
Straight from the approved hours, with nothing retyped elsewhere.
Today: your accounting system, at month end
The platform · included
Everything the service desk needs, from first contact to invoice
The entire service operation, from ticket to invoice, without switching tabs.
- Tickets and SLAs
- CRM and clients
- Projects and timesheets
- Billing and CPQ
- Client portal
- Documents and diagrams
- Password vault
- Reports and NPS
See the platform →
Tickets18 open · 2 past due
#4820Disk at 94% on SRV-BKP-0227 min
#4819Billing office printer offline2 h 10
#4817Onboarding · 3 new workstations1 d 4 h
The RMM add-on · per machine
Monitoring and remote access across the whole fleet
A light agent on each machine, one outbound connection — nothing listens at the endpoint.
- Devices and sites
- Alerts and remediation
- Inventory and patching
- Vulnerabilities
- Automation and scripts
- Remote terminal
- Remote screen
- Audit log
See the RMM →
Devices126 machines · 119 online
SRV-BKP-0294%
NB-VEN-0778%
MAC-DESIGN-341%
Security
The product holds your client's passwords and runs code on their machines
Two halves with different risks: on one side the vault, the contract and the invoice; on the other an agent running with full privilege. What follows is not optional configuration — it is how the product was built.
- One client cannot see another
- Separation is enforced by Row Level Security in Postgres, not by programming discipline. A badly written query returns zero rows instead of the neighbouring client's data — and that holds equally for tickets, assets, documents and the vault.
- The vault records who opened it
- Client credentials live in a per-account vault, with permissions by role and sharing through expiring links. Every access enters the audit log with author and timestamp — whoever opened the client's server password is on the record.
- Second factor and roles
- MFA through an authenticator app, login attempt limits and permissions by role. Across the platform and the RMM, on the same account.
- An audit log you can actually query
- Ticket changes, vault access, remote commands, configuration changes and terminal sessions are recorded with author, timestamp and result. Filterable and paginated, because an audit log nobody can query is not an audit log.
- Remote execution locked in two places
- Running a script requires the server to allow it and the agent on that machine to allow it too, independently. A compromised server alone is not enough to execute code at the endpoint.
- Nothing listens on the monitored machine
- The agent opens an outbound connection to the server. There is no open port waiting for connections, and no inbound firewall rule to negotiate with whoever runs the network.
Pricing
You pay per technician and per machine. That is all.
No setup fee and no surprise on the invoice: the platform is per technician, the RMM is an add-on per machine, and paying a year up front takes 10% off.
2 technicians · 25 machines
R$ 927,30/month
- 2 × R$ 89,90
- R$ 179,80
- 25 × R$ 29,90
- R$ 747,50
5 technicians · 60 machines
R$ 2.243,50/month
- 5 × R$ 89,90
- R$ 449,50
- 60 × R$ 29,90
- R$ 1.794,00
Volume
Above 100 machines
By proposal
the price per machine falls as the fleet grows
- Everything in self-service
- Per-machine price set by the size of the fleet
- Contract with an SLA and a data-protection annex
- Assisted onboarding and a direct line to the team
- Invoiced by bank slip
In every configuration
- Full platform: tickets, SLAs, CRM, projects, timesheets, finance, CPQ, documents, vault and reports
- Client portal
- Public API and webhooks
- MFA and audit log
- Optional white label for R$ 59,90/month
- Annual plan with 10% off
RMM add-on
R$ 29,90
per monitored machine/month
Monitoring, alerts, patching, vulnerabilities, automation, remote terminal and screen. Buy it from 5 machines up, only for the ones you want.
Work out your subscription
The number below is exactly what will be billed. No fine print.
People who log in to Noxus Core
Computers and servers monitored by the agent
- 3 technicians × R$ 89,90
- R$ 269,70
- 30 machines × R$ 29,90
- R$ 897,00
Total per month
R$ 1.166,70
that is R$ 388,90 per technician
On the annual plan it is R$ 12.600,36 per year — R$ 1.400,04 less. You pick monthly or annual at checkout; the 14-day trial applies to monthly.
Prices in Brazilian reais. Monthly means one charge each month, and the 14-day trial asks for no card, unlocking the full platform and the RMM on up to 10 machines. Annual means one charge a year, with the 10% already inside the price, paid up front at signup.
Questions
What people ask before signing up
What counts as a technician and what counts as a machine?
A technician is a person: whoever logs into Noxus Core to handle tickets, run projects or log hours. A machine is a computer or server with the RMM agent installed. They are billed separately: you can have 3 technicians and 80 monitored machines, or 10 technicians and none. Above 100 machines the per-machine price moves to negotiation.
Is it for in-house IT departments or only for people serving clients?
Both. The operation is the same: ticket, SLA, project, logged hours and monitored machine. A service provider uses the client record to separate each company they serve; an in-house team uses it to separate branches, sites or departments — and leaves billing switched off.
Do SLAs respect my working hours?
Yes. First-response and resolution targets are set by priority and counted against the business hours you configure — a ticket opened at 18:05 on Friday does not burn its target over the weekend. And the clock pauses while the ticket sits in Waiting on Client, so the client's time does not become your delay.
Can I use it without the billing side?
You can. Finance and CPQ are there but not compulsory — that is the in-house IT path. Logged hours still earn their keep for sizing the team and justifying a hire, without becoming an invoice. And you do not pay more for not using them: pricing is per technician and per machine, not per module.
Does the client portal carry my brand?
It does, with the optional white label: your logo, colors and domain, for R$ 59,90/month. Without it the portal works the same, under the Noxus Core brand. Either way the client comes in through an email invitation, with no awkward sign-up, and follows the ticket themselves.
Is the password vault meant for client credentials?
That is exactly what it is for. A separate vault per client, permissions by role, and sharing through links that expire — so nobody sends a server password over chat. Every access is recorded in the audit log with author and timestamp.
Do I have to buy the RMM as well?
No. The platform stands on its own as a complete PSA — tickets, SLAs, CRM, projects, timesheets, billing, documents, vault and reports. The RMM is an add-on and you buy it for as many machines as you want to monitor, whenever you want.
Is the 14-day trial limited?
It unlocks the whole platform and the RMM. We ask for a card at sign-up and you can cancel within the period at no charge.
How does the discount work?
The discount comes from paying up front, not from the size of your account: on the annual plan you pay the year at once and take 10% off everything — technicians, machines and white label. Above 100 machines the price leaves the table and becomes a proposal, with a contract and an SLA.
Where is my data held?
On infrastructure in Brazil. Separation between clients is enforced in the database by Row Level Security, not by an application filter.
Can I migrate from the system I use today?
Yes. There is a public API to import clients, contacts and tickets, and the team supports the migration on the volume plan. Talk to us before you subscribe.