Design‑Partner programme
A future design‑partner arrangement would be concrete: weekly engineering sessions, your edge cases in the test catalogue, your policies promoted into the upstream templates, and your name (with consent) on the credits page.
From pilot to production.
The pilot worked. Now the question is what the production deployment looks like — how it scales out to more agents, more tool surfaces, more regulatory frameworks, and how you and your team get supported through that. Here’s the shape.
Editions & commercial posture
Clavenar Lite is Apache‑2.0 and free; the full control plane is sold on a per‑cluster subscription tied to the number of agents and the support tier. We don’t bill by tool call. Pricing is published — no “contact sales for a number.”
What we’ll cover in the 30 minutes.
No slides. You can use a slide if you want; we won’t. The agenda below is what most useful calls look like — we’ll skip anything that’s already obvious for your situation and spend the saved time on whatever is actually unclear.
-
1
Your agent stack, in your words
Which framework, which models, which tool surfaces, how many agents. We’re looking for the shape of the integration, not your roadmap.
-
2
Your threat model
What keeps you up. Where the actual risk lives. Which incidents (your own or industry) have already shaped your posture.
-
3
Pilot shape
Lite or full. One agent or two. Which compliance frameworks have to be visible. What week 3 needs to look like to convince the stakeholder who isn’t on this call.
-
4
What we won’t do
The bits Clavenar won’t solve and the integrations we don’t support yet. The honest version, on the call, not after the contract.
-
5
Next 14 days
Who does what, when. Slack channel, deploy artefact, kickoff date. Two‑sentence write‑up over email within 24 hours.
Request the call.
One form, one email exchange, one 30‑minute conversation. No demo‑mill funnel. We talk to a small number of teams and we like to make those count.
Previous
← Run a two‑week pilot
Or jump to
Technical track →