Unlimited Users, One Price: Why We Never Charge Per Seat

Per-seat pricing is one of the most quietly damaging models in enterprise software — especially for government offices, compliance departments, and investigative teams. When we built Zeph, we made a deliberate decision to never charge per user, and it's shaped how every organization that runs on Zeph actually operates.

What Per-Seat Pricing Actually Does to Organizations

When every user costs money, organizations make predictable compromises. Licenses get shared between people who shouldn't share logins. Part-time staff and contractors get left off the system entirely. Leadership asks "who really needs access?" before every new hire. The software becomes a gated resource instead of an operational foundation.

The consequences are real: incomplete audit trails (who was logged in to that shared account?), information silos (the contractor couldn't see the full record), and version confusion (the Excel export goes to people who aren't in the system). Per-seat pricing generates these problems systematically — and they're invisible until an audit or an incident makes them visible.

Everyone Gets a Real Account

On Zeph, every person who touches your work gets their own account with a real identity, a real role, and a real audit trail. The staff investigator has an account. The administrative coordinator has an account. The contract pathologist who reviews one case a week has an account. The compliance officer who logs in once a month to run a report has an account.

This isn't just about convenience — it's about data integrity. Every action in Zeph is logged against a specific user identity. When an auditor asks who viewed a sensitive record on a specific date, you have an answer. When a court asks who authorized a chain-of-custody transfer, the answer is in the system. That level of accountability only works when every real person has a real account.

Roles Without Licensing Math

Zeph ships with 7 default roles and a fully configurable RBAC Permission Matrix. Module-level and submodule-level access can be defined for every role across 6 modules and 30+ submodules. Administrators can create as many custom roles as they need, assign users individually or by group, and adjust permissions at any time.

None of this requires a licensing calculation. If the deputy investigator needs read-only access to imaging but full access to case notes, that's a configuration decision — not a billing decision. If a new unit needs a custom role with specific permissions, create it. There's no cost associated with user count or role count.

Predictable, Budgetable Costs

Government offices and nonprofits operate on annual budgets that are approved months in advance. Per-seat pricing creates budget uncertainty: every hire, every contractor, every reorganization potentially changes the software line item. Finance asks IT, IT asks the vendor, and the answer sometimes doesn't arrive until after the fiscal year closes.

Flat platform pricing means the cost is known, fixed, and predictable. The software budget doesn't change when you add a deputy. It doesn't spike when you bring on a contractor for a large case. It doesn't require a negotiation when you reorganize departments. One line item, one number, one approval — done.

The Real Cost Comparison

A 20-person office on a typical $75/seat/month SaaS platform pays $18,000 per year just in seat licenses — before support, before storage add-ons, before compliance features. Add 10 more people (contractors, part-timers, read-only reviewers) and that's $27,000/year. Add enterprise security features and you may be looking at $36,000–$50,000 annually.

Zeph's flat pricing covers the full platform for your entire organization — unlimited users, all modules in your selected tier, managed hosting, security, backups, and support. The economics aren't just better. For many organizations, they're transformative.