About Rivet IT Ops
We build self-hosted tools for people who run IT.
Rivet IT Ops is our umbrella for two products. RivetIT is an internal IT operations platform for the IT team inside an organisation. RivetMSP is the version for managed service providers, with multi-client ticketing, dispatch, contracts and billing.
IT teams hold some of an organisation's most sensitive information: network layouts, credentials, asset inventories and the history of every problem they have solved. We think that information should live on infrastructure its owners control, in software they can inspect.
Underneath both sits Rivet Core, a shared library now in beta, so improvements land in RivetIT and RivetMSP together.
That is why both products are self-hosted and developed in the open. You decide where they run, how they are backed up and when they are upgraded, and nothing ties your records to a vendor's cloud.
We develop and provide Rivet IT Ops through FoleyIT LLC. You can reach us through the contact page or at [email protected].
Both projects are released under the GNU General Public License v3.0. Read the licence.
How we build it
We build Rivet IT Ops with AI. Most of the code is written by Claude, directed by a person. Changes go to a beta environment and are tested there before release, and automated tools (CodeRabbit, Semgrep, Aikido) scan the code. People do not review every line.
Built on ITFlow
Both RivetIT and RivetMSP are built on ITFlow, the free and open-source IT documentation, ticketing and asset management platform. All original credit goes to the ITFlow contributors, and we are grateful for the foundation they built.
RivetMSP is a hardened, feature-extended build of ITFlow that tracks upstream and merges its updates. Its additions, such as ticket automation, the Cron Manager, worksheets, calendar sync and SLA tracking on contracts, are maintained by Foley IT / TractorHacker.
RivetIT was developed from that MSP fork and published as ITFlow Internal IT before it was renamed. It reworks the product around one organisation with departments, employees and training.
We are an independent project, and the ITFlow maintainers neither maintain nor endorse our work. Security issues in upstream ITFlow itself belong in its security policy.
Self-hosted
Tickets, docs and credentials stay on your servers.
Open source
Read, audit and extend the code. GPL-3.0.
No lock-in
Your data lives in a database you own.
Built for IT
Shaped by how IT teams and MSPs really work.