Built With a Separate Database Per Clinic

Most practice management software is built by a company that studied the mental health market and then built a product for it. Ritaja Practice started the other way around: a psychologist running his own outpatient practice was spending more than three hours after a full day of sessions on admin split across separate tools for intake, scheduling, notes, accounting, payroll, and report writing. He built one system to replace all of them, used it in his own clinic until it worked, then handed the design to a team to run and build on.

He has no ongoing operational role, access, or relationship with the company today. Ritaja Systems P. Ltd., a government-registered private company founded in 2026 and run independently by Sita Regmi (Director), builds and operates the platform now. The point of the origin story isn’t who runs the company — it’s that the product’s core design decisions were made by someone who had to live with the consequences of getting them wrong, in his own clinic, with his own clients’ records.

The most common way multi-tenant SaaS platforms isolate customer data is a single shared database, with a rule on every table saying “only show rows belonging to this account.” That rule — often called row-level security — works, and it is cheaper to build and run. It is also one line of application logic away from a cross- tenant leak: a query that forgets the filter, a migration that drops the rule, an admin tool that bypasses it by design.

Ritaja Practice does not use that pattern. Each clinic’s data — patients, notes, appointments, billing — lives in its own separate database. There is no shared table for a bug to leak across, because there is no shared table. This costs more to run than the shared-database approach, and it was chosen anyway, before there was a second customer to justify the cost, because a psychologist who has read what a client’s record actually contains does not want “we have a rule for that” to be the whole answer to how one clinic’s data is kept from another’s.

What this means for a clinic evaluating the platform

• A query error or bug in one clinic’s account cannot return another clinic’s records, because the two are not in the same database to begin with.
• A HIPAA Business Associate Agreement (BAA) is required before any real patient data is stored — see the BAA and trust pages for what that covers.
• Every access to a record is logged, with encryption in transit and at rest, on every paid tier — there is no free tier, and no reduced-security version of any tier.

Because Ritaja Practice was built to replace one clinic’s entire admin stack, not to sell an add-on to an existing tool, several things that are commonly separate purchases elsewhere are included on every plan: payroll, full clinic accounting (not just invoicing), staff messaging, unlimited admin seats, and unlimited telehealth video visits. None of this is a claim of being “the best” — it is a structural fact about what one subscription includes, checkable directly on the pricing page and against how the architecture compares to the common shared-database pattern.

No specific customer count or user count is published here or anywhere on the site, and none should be inferred. No third-party review-platform star rating is claimed beyond what is actually shown, unedited, on the reviews page. No SOC 2 or ISO 27001 certification is claimed or implied. The pricing and architecture claims above are specific and checkable precisely so they don’t need to be taken on faith.

Read the full origin story on the About page, the security architecture on the security page, or start a 30-day free trial with no card required to see the platform a working clinic depended on from day one.