SaaS Platforms
Multi-tenant SaaS with separated customer data, Stripe billing and the operations work that keeps it running.
JaSMS: SMS for your platform
Most SaaS products need SMS for verification codes, reminders and alerts. JaSMS is our own Danish SMS gateway with an API for messages and verification codes, and automatic fallback between delivery routes when one fails. Prices from about 36 øre per SMS ex. VAT.
Turning an internal tool or a service idea into software that many companies pay for changes three things at once. Every customer must see only its own data, money has to be collected automatically and correctly, and someone has to notice at night when something breaks. Most SaaS projects that fail do so on one of those three, not on the features.
We know this from running our own. bkg.dk is a booking platform for salons, live since 14 September 2026, with more than a thousand automated tests. JaSMS is an SMS gateway with a customer portal, an admin and an API. danadresse.dk sells Danish address lookups with usage-based billing. JaKonto gives one API over Danish bookkeeping systems. Our time registration and payment reminder products run the same way, and one LynBro account signs a user into eight of them.
Isolation is built into the data layer, not left to each screen: in bkg.dk every query goes through a base repository that adds the tenant, and the platform operator is a separate role. In JaKonto every API route must declare the permission it needs, and a test walks through all routes, so a new endpoint without a rule is closed by default. Billing runs on Stripe: subscriptions, deposits through Stripe Connect, or a usage meter where each address lookup is counted. Stripe events are de-duplicated in the database, and checkouts that never complete are expired by a scheduled job instead of hanging as pending.
Running a SaaS costs more than building it. Each of our products has a scheduled routine that checks health, errors, payments and backups, with a deeper pass at night. Those routines exist because of real incidents: once a platform took payments with a test-mode key while a real customer was connected, and every check was green because none looked at the key mode. Now one does. We quote SaaS work after scoping; development is billed at 500 DKK per hour, and ongoing support starts at 600 DKK per month.
SaaS is the wrong model if you have one customer, which is a custom web app, or if you are still testing whether anyone will pay, which is an MVP. Building tenancy, billing and operations before you have a second customer spends money on problems you may never have.
Key Features
Tenant isolation in the data layer
Every query is scoped to the customer in one shared layer, with a separate role for the platform operator. A forgotten filter on one screen cannot leak another company's data.
Permission rule on every route
Each API endpoint declares the permission it needs, and an automated test fails if any route lacks one. Owner, admin, bookkeeper and viewer roles map onto those permissions.
Stripe billing of three kinds
Monthly or yearly subscriptions, deposits and fees through Stripe Connect, or metered usage where each API call is counted. Webhooks are verified, logged and processed exactly once.
One login across products
Our own OpenID Connect service gives users one account and lets support see the product as a customer sees it, with every such view recorded in an audit log.
API keys with limits
Separate live and test keys, stored as a hash with only the last four characters visible, and keys that can be limited to one action, such as sending verification codes only.
Operations routine per product
Scheduled checks of health, error rates, payments and backups, with a nightly deep pass. Findings go to a queue with a fix or a question for the owner.
Why Choose This Service
Isolation enforced in one layer and covered by tests is easier to explain to a buyer's IT department than rules spread over every screen.
Subscriptions, usage and deposits are charged by Stripe, and failed or abandoned payments are handled by scheduled jobs.
The daily routine checks what the product promises, not just that the server answers.
Login, billing and permissions are shared building blocks, so a second product starts with half the work done.
How We Deliver
Our proven process ensures quality at every step
Decide the tenant model
One database with a tenant column, a schema per tenant, or separate installs. We choose from your customers' size, data rules and how often you will deploy.
Billing before features
Plans, trial, usage limits and what happens when a card fails are designed early, because they shape the data model and the customer portal.
Build with an admin from day one
The operator's admin, audit log and a see-as-customer view are built alongside the product, so support does not need database access later.
Launch behind a switch
Sign-up, live payments and outgoing messages each have their own switch. We turn them on one by one and can roll back a release with one command.
Run it with a routine
After launch a scheduled routine watches health, payments and backups. You get a short report, and anything risky waits for your decision.
Frequently Asked Questions
How do you keep one customer's data away from another's?
The tenant is added to every query in one shared data layer, not in each screen, and permissions are checked on every API route. A test checks that no API route is left without a permission rule. Our own support uses an audited see-as-customer view rather than raw database access, so even we do not browse tenants freely.
Can we charge by usage instead of a fixed subscription?
Yes. danadresse.dk counts every address lookup through a Stripe usage meter and bills overage automatically. You can combine a monthly base with usage, offer a free daily or monthly allowance, or charge per seat. We set up the plans in Stripe and the limits in the product so they agree.
Who runs the platform after launch?
You choose. We can host and operate it on our monitored servers with a daily routine and nightly backups with an offsite copy, or hand it over to your own team with deployment and rollback scripts and the runbook. Many clients start with us operating it and take it in-house later.
Can you turn our existing internal tool into a SaaS?
Often, but tenancy is the hard part. If the tool was built for one company, we first check how deeply that assumption is baked into the data. Sometimes the right path is to keep your tool as is and build the SaaS beside it, moving customers over one at a time.
Does the platform need to be in several languages?
If you sell in Denmark and beyond, plan for it from the start. Our own platforms run in Danish, English and Ukrainian, including the emails they send. Adding languages later means finding every hard-coded text, which costs more than building it in from day one.
Ready to Cross the Bridge?
Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.