Service

SaaS development

We build SaaS the way we build our own: four products of ours are built on the same multi-tenant foundation, so we know what a first version needs and what can wait.

What a SaaS product needs from day one

Some decisions are expensive to change later. We get these right in the first version, and keep the rest as simple as possible:

Tenant isolation: one customer can never see another's data, enforced centrally rather than remembered in every query.
Roles and permissions tied to membership in a customer's account.
An audit log of who did what, from the start.
Reliable background work: notifications go through an outbox with retries, so a failed send doesn't lose a message.
A repeatable release pipeline with automated tests.

Scope of work

Product definition: the smallest version worth launching and what to leave out.
Multi-tenant architecture, sign-in and account management.
Web application, API and admin tools.
Integrations, including payment gateways when the product needs them.
Cloud deployment, monitoring and further development after launch.

Proof: our own products

Kindora, Jazdo, Gralio and Meetapka are AOSOFT's own products, with working demos. In Meetapka, an automated test sends 20 people racing for 2 seats: exactly 2 are confirmed and 18 land on the waitlist. In Jazdo, a shared ledger in the database makes double booking impossible rather than merely unlikely.

Technologies

.NET 10 and Angular 21, PostgreSQL, Google Cloud Run and Firebase, automated API tests and end-to-end tests with Playwright. We also work with Microsoft Azure.

Questions and answers

Can you start with a small first version?

Yes, and we recommend it. Describe your idea and you will get an indicative range for an initial version; the final scope and price are agreed after an individual review.

Custom software development: Business applications, internal systems, APIs and integrations built around how your company works.
Gralio: amateur sports games and venues, with a map of almost 40,000 public places.
Meetapka: shared meals with strangers, where capacity, safety and moderation had to be built in.