If a developer can’t see the price of your tool on your marketing page, you’ve already failed the first trust test.

“Contact sales” has a place in enterprise software. When you’re pricing a 10,000-seat Oracle license that depends on production instance counts, CPU sockets, support tiers, and country-specific compliance requirements, negotiation is part of the product. That’s not dishonesty — it’s complexity made formal.

But for a developer tool? The person who wants to know if they can afford your product is not a procurement manager. They’re someone who landed on your website at 11pm, trying to solve a problem by morning. They want a number. What they get instead is a friction test: fill out a form, wait for an SDR to respond, sit through a demo call, receive a quote that may or may not resemble what they’ll actually pay.

That friction is not accidental. “Contact sales” is a filter — it excludes people who aren’t willing to run the gauntlet, and it creates headroom for the sales team to price-discriminate. Both are features in certain business models. But they are fundamentally incompatible with the kind of trust a developer tool needs to earn.

Developers talk. If your per-seat price is one number for an individual and a radically different number once an organization has 200 licenses, that gap becomes a Hacker News thread within six months. The opacity doesn’t protect the price. It just delays the disclosure long enough to feel like a betrayal.

The test is simple: can a developer read the price, decide whether it’s worth it, and subscribe without talking to anyone? If the answer is no, ask why not.

For Veesker the answer is yes by design. The Community Edition is free under Apache 2.0 — download it, use it, ship with it, no payment required. The Cloud layer — arriving H2 2026 — is $29 USD per seat per month, one tier, every feature included. No sales call. No annual-only contracts buried in footnotes. No per-feature paywalls that appear after you’ve already integrated. Founder pricing for waitlist members is locked at that number now, before the product ships, so there is no bait-and-switch when GA arrives.

That’s not a marketing decision. It’s a philosophical one. A developer who downloads Veesker should know exactly what happens if they decide to upgrade to Cloud one day. The number is on the page. The decision is theirs.

Developer trust is slow to earn and fast to lose. A pricing page that shows the number is the minimum expected — but a surprising number of tools still get this wrong. Don’t be one of them.

Join the waitlist and lock your founder rate before Cloud GA.

— Veesker