Free software is not free to operate. Somebody still pays for the hosting, the AI tokens and the hours. The only question is who. That’s the commercial problem we’re working on, because we want DeltaVault in the hands of as much of the Data Vault community as we can manage. That means no “contact sales” gate and no mysterious enterprise price that scales with the size of your company. It also means no data modeling tool sitting idle while you wait for budget sign-off. In practice, the goal is as close to free as we can reasonably get.

The community needs a common tool

There is a bigger opportunity here than selling another Data Vault product.

We want DeltaVault to become a common modeling environment that the Data Vault community can actually use, learn from, and help improve. That doesn’t mean contributing to the DeltaVault codebase, as you would to an open source project. It means contributing to the solution around it: templates, AI skills, modeling patterns, feedback, ideas, and the lessons that only come out of real implementations. The more people working in the same environment, the more of that collective experience can be turned into something useful for everybody.

None of that happens unless you can get access in the first place. Historically, specialized data warehouse automation software hasn’t been famous for being inexpensive, and often you can’t even find the price on the website. If the price of your software can’t be published, is that a warning before the sales conversation has even started?

Unfortunately, somebody still gets the bill

Making software inexpensive doesn’t make its operating costs disappear. There are at least three meters running behind DeltaVault, and every one of them keeps ticking whether or not anyone is paying.

Infrastructure costs money. Every account, model, version, process and stored piece of metadata consumes compute and storage somewhere. That consumption grows with your usage, not with our price list.

AI costs money. Every time we send context to a language model and ask it to analyze, propose or generate something, a provider charges us for that operation. There is no free tier hiding behind the feature.

Support costs money. Documentation and community discussion scale reasonably well, because one good answer serves many readers. Individual support doesn’t work that way. An hour spent helping one person is still an hour of someone’s time.

Declaring the product free solves none of this. It only moves the bill. Eventually somebody still has to pay it.

Free cannot mean unlimited

Some parts of DeltaVault cost almost nothing when another user shows up, and those are exactly the parts we want in as many hands as possible. Other parts carry a real cost for every additional unit of consumption, and AI is the obvious example. Unlimited AI usage for zero dollars isn’t a software pricing model. It’s a delayed invoice for the company providing it. Infrastructure and individual support follow the same logic soon enough.

So the objective probably isn’t to make everything free. It’s closer to removing the software price tag wherever possible while being transparent about the things that genuinely cost money.

That’s a far more sustainable definition of free.

Free shouldn’t be temporary

Launching a generous free tier is easy. Sustaining one is much harder once thousands of people are using it every day. The cost curve keeps climbing long after the announcement has been forgotten.

When the economics don’t work, the outcome is predictable. The free tier quietly disappears. Or the limits tighten until nobody can use it for real work. Or the company starts hunting for other ways to extract enough revenue to cover the gap. None of that helps the community that showed up in the first place.

We’d rather start with a model that can survive its own success.

Where should a free tier draw the line?

Here’s where we’ve landed so far. The core DeltaVault experience should be as accessible as we can make it. AI usage stays transparent and measurable. Bring your own key is in the design. DeltaVault is built to run on your own Anthropic key, where the deployment has that switched on. Your plan decides the support level. And the price will be published, not something you have to request.

There may be another part to the answer, though. If the community is helping make DeltaVault more valuable for everyone, then contribution itself should carry value. Could somebody who contributes a useful template earn DeltaVault credits? The same goes for a reusable AI skill, a modeling pattern, or detailed product feedback that improves the application for everybody. Put another way, could contribution become another way of paying for usage?

That would get us closer to the goal: a community modeling tool where the people who help make the ecosystem better can also use more of it for free. Making that fair without creating another problem is the next commercial challenge, and you can help us work it out. If you’d contribute a template, a skill, a pattern or feedback, tell us what a fair credit for it looks like.