Oriental Nippon Development

Engineering

Multi-Tenant SaaS & Identity

An identity decision decides what your business can sell.

We modernise authentication and authorisation onto open identity services, add tenant isolation, subdomains and custom domains, so one deployment serves many customers safely.

Ideal for

  • Companies with a proven internal system
  • B2B platforms
  • Healthcare and welfare software vendors

What we deliver

Multi-Tenant SaaS & Identity: what's included

Tenancy boundary modelling
Ory Kratos identity
Ory Keto permissions
Tenant-scoped data access
Subdomain and custom-domain routing
Migration without password resets

How we work

How we deliver

  1. 01

    Understand the job

    Map user journeys, edge cases and operating reality.

  2. 02

    Architecture & foundation

    Environments, CI/CD and a modular structure that fits your scale.

  3. 03

    Thin vertical slices

    Ship working features end to end, every iteration.

  4. 04

    Integrate for production

    Retries, idempotency, logging and tests on every integration.

  5. 05

    Pilot with real users

    Test where the software is actually used.

  6. 06

    Hand over or run

    Docs, ADRs and handover sessions, or we operate it for you.

See how we work with you

Outcomes you can expect

What changes for you

One deployment, many customers
Isolation enforced on every request
Enterprise-ready access control
A product you can sell

Technologies we use

Focus areas & technologies

Frequently asked questions

Multi-Tenant SaaS & Identity: frequently asked questions

How do you scope a Multi-Tenant SaaS & Identity engagement?

We start with a short discovery, usually one to three weeks, to map the process, data and constraints, then propose a phased plan with clear milestones and costs.

Which engagement model fits?

SES suits teams that want specialist engineers under their own management; a Lab-type ODC suits long-term product work; an R&D Lab suits proving an idea before committing. We often start with one and switch as needs change.

Who owns the code and infrastructure?

You do. Code, infrastructure definitions and data live in your accounts and repositories from day one.

Do you work in Japanese?

Yes. Our bilingual bridge team coordinates requirements, reviews and reporting in Japanese and English.

Get started

Start building smart
with Oriental Nippon today

Book a 30-minute call. We'll suggest a team, an engagement model and a first milestone.

Book a call