Skip to content
LorienSoft

Web platforms builtto be maintained.

Customer portals, SaaS products and internal tools on Next.js and TypeScript. We design the architecture with the people who will run it, so later releases stay as easy to ship as the first.

What a web platform build includes.

  1. 01

    Product and portal builds

    Authenticated applications with roles, workflows and reporting, scoped around the tasks your users need to complete.

  2. 02

    SaaS foundations

    Multi-tenancy, subscription billing, usage limits, an admin console and an audit log.

  3. 03

    Marketing and content sites

    Fast, accessible sites with editorial workflows, preview environments and structured content that marketing can change without a release.

  4. 04

    Headless CMS integration

    Content modelling and integration with Sanity, Contentful, Strapi or Payload, with draft, review and publish flows that match how your team works.

  5. 05

    Performance and accessibility

    Core Web Vitals budgets set before the build and enforced in CI, with accessibility tested by keyboard and with real screen readers.

  6. 06

    Legacy replatforming

    Incremental migration from PHP, .NET or older single-page codebases, route by route, behind your existing domain.

Typical web projects.

  • Replatforming a legacy PHP portal to Next.js

    New routes are served from Next.js behind the existing domain while the old application keeps running. Traffic moves route by route, with redirects and parity tests, until the legacy code can be switched off.

  • A B2B SaaS, from prototype to paid pilot

    A validated prototype is hardened into a multi-tenant product with billing and an admin console, and made ready for its first paying customers.

  • An internal operations tool that replaces spreadsheets

    We model the real workflow, import the existing data, and give operations staff a tool with permissions, history and exports they can trust.

From route map to runbook.

  1. 01

    Agree the scope

    We map user roles, key user flows and integrations, then agree what is in the first release and what is deliberately left out.

    You get
    Scope document and route map
  2. 02

    Lay the foundation

    Repository, CI, preview environments, authentication, design tokens and observability are in place before feature work starts.

    You get
    A running skeleton in staging
  3. 03

    Build in vertical slices

    Each sprint delivers a working feature from interface to database, behind a feature flag and ready to demo.

    You get
    Releases to staging every sprint
  4. 04

    Harden and hand over

    Load, accessibility and security checks, runbooks, and a walkthrough for your engineers. We stay on for support if you want us to.

    You get
    Runbook and a documented release process

The web stack we build on.

If your team already runs on something else, we work within it.

Frameworks

  • Next.js
  • React
  • TypeScript
  • Astro

Data

  • PostgreSQL
  • Prisma
  • Drizzle
  • Redis

Content

  • Sanity
  • Contentful
  • Strapi
  • Payload

Delivery

  • Vercel
  • AWS
  • Docker
  • GitHub Actions

Quality

  • Playwright
  • Vitest
  • Lighthouse CI
  • axe

Stack, ownership and what happens after launch.

Both. If you have a team and conventions, we work inside them. For new products we usually recommend Next.js and TypeScript with PostgreSQL, and we set out the trade-offs in writing before you commit.