Product engineering

SaaS, portals, and web apps that actually ship.

We architect, build, and deploy custom software for Australian businesses, without the agency overhead and without months of stalled discovery.

The work

From idea to production, with one team.

We build internal ops portals (rostering, work orders, headcount tracking, PIN-gated shop-floor tools), customer-facing SaaS (with billing, multi-tenancy, real auth), and the bridging web apps that sit between an enterprise's BI and its operations team.

Our default stack is SvelteKit + FastAPI + SQL Server, chosen because each piece earns its place. SvelteKit gives us small, fast bundles and a sane developer experience. FastAPI gives us typed, fast, well-documented APIs without the .NET overhead. SQL Server because that's what most AU enterprises already license.

We don't chase frameworks. We don't lock you into a black-box runtime. The code we hand over is the code you can read, modify, and host yourself if we ever part ways.

Capabilities

What we build inside this practice.

SaaS platform architecture

Multi-tenant, properly bounded, with billing, auth, and a deployment pipeline that doesn't need a person to babysit it. We design the platform you can grow into for two years before you outgrow it.

Internal ops portals

The kind of system every operations team actually wants: rostering, shift control, headcount tracking, work-order management. SvelteKit + FastAPI + your existing SQL Server.

Customer-facing web apps

Self-service portals, ordering experiences, analytics dashboards delivered as a product. With proper auth, billing, and tenant isolation.

Mobile applications

iOS and Android via React Native or Capacitor when a native shell is required; PWA when it isn't. We prefer PWA for ops tooling, because install friction matters less than iteration speed.

API & third-party integrations

Stripe, Xero, MYOB, HubSpot, Twilio, Slack, Teams. Plus bespoke API clients for the systems your customers depend on.

Performance & refactor work

When a SaaS has grown organically and needs an architecture pass: query plans, caching, background jobs, isolation between fast and slow paths.

Stack

What we work with.

Boring, proven, maintainable. We are deliberately not at the bleeding edge. We ship on stacks that have at least two years of production track record under our belts.

Frontend: SvelteKit 2 + Svelte 5 · React + Next.js (when required)
Backend: FastAPI (Python) · Node.js · .NET (when integrating into Microsoft estates)
Database: SQL Server · PostgreSQL · MSSQL (mssql client) · SQLite for embedded
Hosting: Azure App Service · Cloudflare Pages + Workers · NSSM-packaged Windows services
Auth: Bespoke session-cookie + role gate · Entra ID / Azure AD SSO
Payments / billing: Stripe · Xero · MYOB integration

Start with a scoping sprint

Two weeks. You get an architecture, a plan, and a fixed price.

We don't run open-ended discovery, and we don't quote a build we haven't thought through. The middle path is a short paid scoping sprint that ends in something you can actually act on.

We sit with the people who will use the thing, map the domain, choose the architecture, and put a clickable prototype of the core workflow in front of you. Then we price the build against that, not against a guess.

The prototype and the written architecture are yours regardless of who builds it. If the right answer turns out to be an off-the-shelf product rather than a custom build, we would rather tell you in week two.

FAQ

Frequently asked

What stack do you build SaaS on?

Default is SvelteKit on the frontend, FastAPI (Python) on the backend, and SQL Server or PostgreSQL for the data layer. Hosted on Azure App Service, Cloudflare Pages + Workers, or self-hosted on Windows via NSSM when the customer requires it. We don't change stack chasing trends. These tools ship reliably and stay maintainable.

Will you also handle hosting and deployment?

Yes. We set up CI/CD (GitHub Actions or Cloudflare deploy), provision infrastructure, configure observability, and document the runbook. You can take it from us cleanly later, or we can stay on retainer for ongoing ops.

Can you work with our existing dev team?

Often. We come in as senior support: architecture review, performance work, getting a stalled project unstuck, building a specific module the in-house team hasn't had time to ship. We don't insist on greenfield.

What about authentication and user management?

We've built bespoke auth (session cookies, role-based gates, PIN-based shop-floor entry) and integrated with Azure AD / Entra ID for enterprise SSO. Pick what fits. Most ops portals don't need full enterprise SSO, though some do.

How long does a typical build take?

A pragmatic internal portal: 4 to 8 weeks to first usable version. A customer-facing SaaS with billing, multi-tenancy, and integrations: 4 to 6 months for an MVP that survives real users. We do fixed-scope sprints, not open-ended discovery.

Other things we do

Data Intelligence

Have a product that needs to ship?

Tell us what you want to build. We'll tell you what we'd scope, what we'd defer, and what it would cost.

sales@onsignal.com.au Start a Conversation