Where we are
Where is Pillar today?
Pillar is being built with design partners, on their real estates, against their real recovery commitments. General availability is planned for 2027. What this site describes is what we are building with them.
Can we buy Pillar now?
Not yet. There are three ways in today: ask us to walk you through it, join as a design partner, or sign a non-binding letter of intent to buy, which puts you at the front of the line for general availability. Pricing is being set with design partners, so if you tell us about your estate and the services you would want to see, the conversation starts there.
Who is building Pillar?
A small founding team: fifteen-plus years in infrastructure operations, asset management, data protection and enterprise architecture; a former Veeam engineer; a decade building software in a highly regulated industry and in government; and experience inside a large healthcare organization, in legal and privacy, and as a CIO.
Design partnership
What does a design partnership involve?
We run Pillar on your real estate, against your real recovery commitments, with you, before general availability. You see your services, their dependencies and their evidence as Pillar builds them; you tell us what is wrong and what is missing; you shape what ships. The pilot costs nothing.
What do we need to give you?
Read-only access to your data protection platform’s API, which today means Veeam Backup & Replication’s REST API; a named owner on your side; and the recovery commitments for a handful of services to start with. Discovery is agentless and credentialed, so there is nothing to install on the machines Pillar maps.
What happens to our data?
Pillar reads what your data protection platform records about your backups: jobs, retention, restore points, backup infrastructure, replicas and sessions, the list on the Pillar for Veeam page. It reads the platform’s records, not the contents of the backups themselves. What we hold about you as a design partner, and for how long, is in the privacy policy.
Why Veeam first
Why Veeam first?
One of us is a former Veeam engineer, so we saw the software develop and saw its roots in infrastructure. Our team has also spent time on the operational and governance side, from a ServiceNow perspective. We saw an opportunity to take the best of what Veeam provides, particularly in proving that data is actually recoverable, and apply our IT operations experience to build an application-level proving engine, aligned to a service, that meets governance.
When do Rubrik, Commvault and the others come?
They are being built now. The Rubrik and Commvault pages say what Pillar will read from each and how each verifies a restore. Pillar is designed for several providers from the start, because most estates run more than one. If you run something else, ask about yours.
Why now
Why now?
Because continuity has become something you evidence to a regulator, not something you assert, and the evidence is still assembled by hand. Independent research keeps finding the same three gaps: teams cannot see recoverability at the service level, the proof behind the recovery plan is put together by hand, and continuity now has to be shown to someone who will ask. Data protection knows what is running. The business knows what it needs. Nobody holds both, and nobody can keep the join current by hand. That is the gap Pillar closes.
Doesn’t our backup platform already do this?
It does half of it, and does it well. Veeam, Rubrik and Commvault know what was backed up, when, whether the job succeeded and whether a restore point exists. They do not know which business service any of it serves, who owns that service, or what the recovery commitment is. Pillar reads what they know, composes it by service, and hands the result back to the tools you already run. It replaces nothing.