In development · not yet generally available
One product, not five acquired ones.
Saldera is a professional services automation platform for small MSPs — service desk, sales, billing — with remote monitoring designed alongside it rather than bolted on afterwards. One codebase, one design language. It is built by someone who runs an MSP, it is not finished, and this page says exactly how far along it is.
Why build another one
The big platforms are collections of acquired tools.
The incumbents grew by acquisition, and the seams show in every workflow: the ticketing module and the billing module were different products, written by different companies, and they still behave that way. A three-to-six month implementation with a paid partner is treated as normal. Pricing is quoted, not published.
The alternative most small MSPs land on is five or six tools — PSA, RMM, documentation, password manager, spreadsheets, a client portal — and a person re-typing the same client details into each one.
Saldera is one codebase with one design language, so the parts agree with each other by construction. The AI features read the same data the rest of the application does, rather than a synchronised copy of it. That coherence is the entire bet.
What is in it
Built, being built, and planned — marked honestly.
Where we are
Nothing is live yet.
Saldera runs in development, on real data belonging to the MSP that is building it. It has not been deployed to production, no customer is using it, and there is nothing to buy. The first milestone is one MSP running its whole business on it; general availability comes after that.
Most companies at this stage write a launch page and imply the product is further along than it is. We would rather you know what you would be looking at.
True today
- A ticket can arrive by email, get an SLA, collect time, and be answered with an AI-drafted reply a person approves.
- A lead form can become a proposal, get signed by two people in order, and produce a signed PDF with an audit trail.
- An invoice can be generated on a recurring schedule with its prices frozen at send.
- A Syncro tenant's history can be imported and the run resumed if it breaks.
- AI features are metered per tenant against a budget, and the cost of each run is recorded.
Not true yet
- No money moves. Nothing charges a card or writes a payment.
- No client portal pages exist, and there is no self-serve sign-up or trial.
- Our own RMM has a specification and no code. Remote access will use an integrated third-party tool at first.
- There is no MCP server yet, whatever our older documents claim.
- There is no accounting export. QuickBooks Online is first in line.
- Email and file storage are still on vendors being replaced, and the production environment cannot boot until several accounts exist.
Last updated 17 September 2026. This page is revised when the answer changes.
Positions we have taken
Four decisions that are hard to reverse later.
One product, not a portfolio
Service desk, sales, billing and monitoring are being designed together in one codebase. It is slower to start and it is the only way the seams disappear.
Built to handle health data from day one
Most MSPs have a medical or dental client, so ticket text will contain patient details. Every vendor in the stack was chosen for whether it would sign a business associate agreement, before the first customer — not retrofitted afterwards.
Payment pricing in the open
One published rate for cards and one for bank transfers, no volume tiers, and dual pricing done the lawful way: a card price and a bank price, never a surcharge added at checkout. The MSP nets the invoice amount either way.
AI included, and metered
An allowance per technician each month, credit packs beyond it, and bring-your-own key if you would rather pay the model provider directly. AI-written text that goes to a client is approved by a person first.
Subscription pricing sits on one axis — per technician, per month, with the core features included. The number comes from what the pilot actually costs to run, so it is not published yet.
Design partners
We need three to five MSPs to tell us we are wrong.
Right now one MSP's way of working is shaping the entire product, which is a good way to build something that fits exactly one company. We would like to hear "that is not how we do it" while changing it is still cheap.
Look at it every few weeks and say what is wrong. That is the whole commitment — a shared development environment or a recording, a conversation, and your objections written down as issues. No cost, no contract, and no obligation to use it afterwards.
Who we are looking for
- One to ten technicians, twenty to a hundred clients
- United States, for now
- Especially if you run ConnectWise, Autotask or HaloPSA — we already know Syncro well
What you get
- Influence over an unfinished product, on the parts you actually touch
- A clear view of what is real, at any point
- First access when the pilot opens up
What we will not do
- Put your real client data anywhere near a development environment
- Ask you to switch anything
- Add you to a mailing list