Blissfully was acquired. Zylo starts at enterprise pricing. There's no good option between a spreadsheet and a $500/month platform — so we built one.
At the high end, tools like Zylo and Torii do excellent work — for companies with 500+ employees, a dedicated IT team, and a procurement function. Their starting price reflects that audience.
At the low end, the answer is usually a shared spreadsheet in Notion or Google Sheets. That works for six months, then someone stops updating it, and the data drifts until it's misleading rather than useful.
Subrina is the tool that should exist between those two ends — purpose-built for 10–100 person companies, priced at $19/month, and designed so that an ops manager can set it up in an afternoon without a vendor onboarding call.
I'm a Java / Spring Boot developer who has spent years building backend systems. Subrina started as a weekend project when I noticed that the US startup market had no affordable, focused tool for the SaaS management problem.
The goal is simple: build the product that fills the gap, price it honestly, and make it good enough that you'd miss it if it disappeared. No enterprise upsell path. No pivot to some adjacent market. Just a useful tool at a fair price.
Target: live and deployed within six months of starting. If you have feedback, I want to hear it.
Subrina doesn't hide the cancel button, inflate seat counts to trigger upgrades, or lock your data behind a paywall when you downgrade. If you want to leave, export your data and go. We'd rather earn retention than engineer it.
We collect what's needed to deliver the product and nothing else. Email bodies are processed in memory and never stored. OAuth tokens are encrypted at rest. We're not building a data business — we're building a productivity tool.
Three plans with published prices and a clear feature list. No custom pricing tiers revealed only in a sales call. No features artificially removed from lower tiers to push upgrades. What you see on the pricing page is what you pay.
Features are designed for a single ops manager or finance lead, not for a procurement team of 10. Complexity is a product decision, not a necessity. If a feature requires an onboarding session to understand, we'll redesign it.
Subrina ships frequently. The roadmap responds to what users actually need, not what was planned 18 months ago. If you report a bug, it gets fixed in days, not the next quarterly release. Single-person team advantages are real.
This isn't a startup built to be acquired. It's a product built to be useful and to sustain itself as a business. If you put Subrina at the center of your ops workflow, you should be able to rely on it still being there in three years.
Feature requests, bug reports, or just a note about what you need — all of it helps.