Open source. $0 to run.
orvacon is a library you install, not a service you rent. There's no paid tier today — every package is MIT-licensed and runs in your own infrastructure.
No per-transaction fee, no seats, no usage metering. You run it; you pay nothing to us.
No credit card, no sign-up, no license key. bun add @orvacon/paykit and you're running.
You pay your gateway. Not us.
A payment has real costs — but they're charged by your gateway and your infrastructure, the same as if you'd integrated by hand. orvacon adds nothing on top, because it's never in the money path to take a cut.
Illustrative split — exact gateway and infra costs depend on your provider and scale.
Things we don't charge for.
Per-transaction fees
We don't sit in the money path, so there's no transaction to skim. Volume costs you nothing extra here.
Per-seat licenses
Your whole team can use it. There are no seats to count and no per-developer pricing.
Feature gating
No "enterprise-only" lock on security. Ed25519 webhooks, RLS and the ledger are in the box for everyone.
A hosted middleman
There's no orvacon cloud to pay for or trust. It runs entirely inside your own runtime.
How a free project keeps going.
orvacon is open source and maintained in the open. If it's useful to your business, sponsoring its development is the best way to keep it healthy. Sponsorship is optional — it never unlocks features or changes the license.
MIT is MIT. A version you depend on stays free, forever.
Any future managed offering would be opt-in and additive — never a paywall over the open-source core.
Straight answers.
Is it really free?
Yes. Every published package is MIT-licensed and there's no paid tier today. You pay your gateway and your own hosting — orvacon itself costs nothing.
Is there an enterprise plan?
Not right now. Security features aren't gated behind a tier — everything in the project is available to everyone.
Do you take a cut of payments?
No. Funds move on the cardyour gateway account path; orvacon is never in it, so there's nothing for it to skim.
How can I support it?
Sponsor on GitHub, contribute code or connectors, or report issues. All optional, all appreciated.
Nothing to buy.
Just start building.
Install the packages, point a connector at your gateway, and ship. If it earns its place in your stack, sponsor it.