RIVET99 is being built to bring the work around MSP service into one connected system: customers, tickets, devices, documentation, and the handoffs between them.
In development Phased release MSP-first
A concept of the intended service context, not a product screenshot or a claim of shipped functionality.
Build principles
A stronger MSP ecosystem.
01 / Platform blueprint
One shared customer context, from a technician’s queue to a business owner’s portal. Here’s the plan—and what is still being developed.
COMMAND, DOCS, and CONNECT are planned to bring the core together: customer records, ticket assignments, dispatch, asset records, documentation, and a customer-facing portal.
Planned shared records and permissions aim to reduce lost context.
Roadmap / FLOW
The planned automation engine is intended to coordinate onboarding approvals, IT tasks, equipment, licensing, and completion updates—with human approval where it matters.
Roadmap / PULSE + integrations
N-able, Freshservice, and Microsoft 365 are integration priorities. Phased adoption is the goal; availability depends on verified APIs and permissions.
Longer-term roadmap
VAULT · SHIELD · PROJECTS · PEOPLE · FINANCE · INSIGHT · ASK RIVET
Planned areas include credentials, security, field work, employee operations, billing, reporting, and permission-aware AI.
02 / Plans & adoption
Commercial pricing is being evaluated. Confirm plan availability, included modules, migration scope, and billing terms before subscribing; roadmap modules are not included unless explicitly stated.
For individuals getting started
$0/month
03 / Build the next chapter
Bring your queues, handoffs, and operational headaches. Help shape an MSP system built for the way your team actually works.
Interest registration is not a promise of immediate access or a live product demo.