Rinjani is built end-to-end by an independent developer and builder, in early access. Self-serve billing isn't wired up yet, so the two paths below are what's actually available today. The roadmap further down explains what comes next.
Self-host
Run the full platform on your own infrastructure. Same engine the managed service runs on.
Managed hosting — we run the platform, you read the briefings
Direct line to the engineering team via shared Slack
Custom feed onboarding for sources we don't ship with
Locked-in pricing for 24 months once self-serve billing goes live
Influence on the roadmap — features you sponsor ship faster
What it costs you
Annual commitment, invoiced
Pricing scoped to your team size + workload — typically $4k–$12k/year for early partners
Some patience: built end-to-end by an independent developer and builder — response times are next-business-day, not next-hour
Where pricing is heading
The roadmap — so you know what you're signing up for
I'd rather under-promise here than ship a fancy tier table I can't back up. These three stages are the real plan; the dates flex based on when founding-partner conversations land.
1
Now (mid-2026)
Self-host + founding partners
Public repo, OSS-friendly license. Managed pilots onboarded one-by-one via email + invoice. No self-serve billing yet — and I won't pretend otherwise.
2
When 8 founding partners are live
Self-serve billing for small teams
Stripe-backed self-serve for teams under ~25 seats. Tier pricing will be published the day this goes live. Founding partners stay on their original contract.
3
After self-serve is stable
Enterprise plans + procurement docs
SOC 2 attestation, DPA + custom-contract paperwork, SCIM provisioning, dedicated support tier. Until then, founding-partner agreements cover the same surface manually.
Frequently asked
Why no published tier pricing right now?
Because as an independent developer running this end-to-end, I haven't talked to enough customers yet to know what the tiers should be. Publishing numbers before that would be a guess, and the numbers would change once real customers told me they were wrong. Founding partners get the conversation that informs the eventual pricing.
Is the self-hosted version really the same as the managed one?
Yes. There's no "open-core" hold-back. Everything in the GitHub repo is what runs in production. The reason to pay isn't to unlock features — it's so you don't have to operate the infrastructure.
What does "locked-in pricing for 24 months" mean?
When self-serve billing launches, founding partners stay on whatever rate we agreed on for two full years — even if the published tier rate is higher. After 24 months you can renew at the then-current rate or move to a published tier.
Can I bring my own LLM keys?
Yes, on both paths. Drop OpenAI / Anthropic / Gemini keys in your .env and the platform routes through them with per-key rate limits. Ollama works for self-hosted models. This isn't a paywall.
Do you offer non-profit / academic terms?
Yes. Founding-partner pricing is already discounted; for non-profits and academic teams I'll halve it again. Email from your institutional address.
What happens if you stop working on this?
The repo is MIT-licensed. You can fork it, run it forever, and self-host whatever's there at the time. That's an explicit promise — I'd rather customers know that than worry about lock-in.
Still not sure which path fits?
Email and I'll tell you straight whether self-hosting or the managed founding-partner path makes more sense for your team. I won't push managed if self-hosting is the better answer.
