Corewell SystemsSaaS Platforms
Product-grade platforms that serve many customers from one codebase, with accounts, billing, and updates included.
The problem it solves
Turning a working system into a platform others can subscribe to is a different engineering problem: many organizations on one codebase, each with its own users, data, and settings. We build multi-tenant platforms that stay fast, private, and updatable as the customer list grows.
What's included
- Multi-tenant architecture with strict data isolation
- Subscription and billing integration
- Admin and customer-facing dashboards
- Usage analytics and reporting
- Scalable cloud deployment
Evidence
What we have actually built
Each entry below exists in a system we designed and shipped. Client and product names are withheld by policy. The engineering is not.
Isolation enforced three levels deep
Customer data is separated by organisation, by site within that organisation, and by which sites each user may reach, with the final boundary enforced by the database itself, so one customer's records stay unreachable even if application code were at fault.
Every customer configured independently
Each organisation runs on its own subdomain with its own plan and limits, and each of its sites carries its own time zone, tax and facility identifiers, feature toggles, and even its own payment account, all from a single deployment.
Billing that actually controls access
We have built subscription billing where a lapsed payment automatically withdraws the customer's listings across the platform and a successful payment restores them, driven by the payment provider's own events rather than a nightly script.
Platform revenue built into the transaction
For platforms that process payments on behalf of their customers, we implement per-transaction platform fees with different rates for online and in-person payments, configurable per site, while each customer keeps their own merchant account and settlement.
One API, many clients
The same interface serves the web application, a companion mobile app, and purpose-built tablet devices, so every rule is enforced once, on the server, rather than reimplemented per client.
Where this shows up
Industries where we have delivered this capability. It applies well beyond them. These are the ones with systems behind them.
Under the hood, for technical buyers
Multi-tenant PostgreSQL and SQL Server designs using row-level security and request-scoped tenant context, subscription and marketplace billing with idempotent webhook reconciliation, background job processing, structured logging, and infrastructure as code.
Full technology stack, and why we chose it →Straight answers
SaaS Platforms, answered plainly
What buyers ask before committing. Short answers, no hedging.
How is customer data kept separate on a shared platform?
At three levels, with the last one enforced by the database itself. Data is separated by organisation, by site within that organisation, and by which sites each user may reach, so one customer's records stay unreachable even if application code were at fault. This is engineering we have shipped, not a configuration setting.
Can each customer have their own settings and branding?
Yes. In the platforms we have built, every organisation runs on its own subdomain with its own plan and limits, and each of its sites carries its own time zone, tax and identification details, feature toggles and even its own payment account, all from a single deployment.
How does subscription billing control access?
Automatically, driven by the payment provider's own events rather than a nightly script. We have built platforms where a lapsed payment withdraws that customer's listings across the whole platform and a successful payment restores them, with the customer's dashboard gated on every navigation.
Can the platform earn a fee on transactions it processes?
Yes. We implement per-transaction platform fees with different rates for online and in-person payments, configurable per site, while each customer keeps their own merchant account and settlement, so the platform earns without ever holding the customer's money.
Related reading
- Custom Software vs. Off-the-Shelf: How to Decide for Your BusinessA practical decision framework: when a ready-made tool is the right call, when a custom build wins, and how to compare the real five-year cost of each.
- What Does Owning Custom Software Actually Save You?The real return on owning custom software: recovered hours, plugged revenue leaks, replaced subscriptions, and a business that runs on numbers not memory.