Skip to main content

Dev Station Technology

Software product development

Building software that strangers pay to use

A product needs tiers, tenants, licensing, onboarding and a way to ship without breaking existing customers. We have built products and internal tools, and they are different jobs.

Decisions before the first line of code

Who is the tenantCompany, site or individual
What separates tiersFeatures, limits or seats
Can a customer self-serveSign-up without you
Who hosts itYour cloud, or theirs
How you shipEveryone at once, or per tenant

Change these later and you rebuild. Decide them first and you do not.

2Tiers shipped from one codebase on Hydrajaws
500%Rise in potential clients after that launch
MultiTenants isolated on one IoT Workz deployment
100%Platform ownership handed to IoT Workz
What we build

The parts of a product that internal tools skip

A product platform, from sign-up to release
Customers
Self-service sign-upNo call with your team
Tiers and entitlementsLimits enforced on the server
Product
Tenant separationIsolation at the data layer
White labellingBranding without a fork
Delivery
Your cloud or theirsSelf-hosted where buyers insist
Release pipelineOne customer upgrade, not everyone outage
Identity
KeycloakSingle sign-on and roles
Azure logo
Azure AD B2CWhere customers sign themselves up

Billing stays with the provider you choose. We enforce entitlements against it and do not write payment processing.

Fit check

Is this a product build?

Pick us when

  • Strangers pay to use it
  • Customers must never see each other data
  • Tiers or seats decide what is available
  • Some customers want it running in their own cloud

Look elsewhere when

  • One organisation uses it and every user works for you
  • You control when everyone upgrades
  • Nobody is billed for using it
  • A handful of buyers will each demand their own instance
Product parts

Four parts that decide whether it can be sold

What separates a product from a tool
Tenant separationEnforced on the server. We ran many tenants on one IoT Workz deployment.
Tiers and entitlementsFree and paid from one codebase. Hydrajaws ships exactly this.
White labellingCustomer branding without a fork per customer, which makes reselling possible.
Release without breakagePipelines and regression, so one upgrade is never everyone outage.

A product forks per customer the first time one reasonable exception wins. Configuration does the work a fork would do.

How the work runs

The smallest sellable thing first

From commercial shape to first customer
Week 1

Commercial shape

Tenants, tiers, pricing and delivery. These decide the architecture, so they come before features.

Weeks 2 to 4

Architecture and prototype

Isolation model, identity and a clickable prototype of the paid path.

Weeks 5 to 16

Build to first customer

Aim at something one real customer can buy. Demo every two weeks.

After launch

Ship repeatedly

Pipelines, a regression suite and a release process your team can run.

A first sellable version takes 10 to 14 weeks. Tiers, tenant isolation and self-service sign-up add to that.

Technologies

What products run on

Linked tiles open the page with the builds and the fit check.

Builds

Two products, two delivery models

Hydrajaws safety testing app built by Dev Station
Case study, United Kingdom

A free tier that sells the paid one

The client wanted to reach more of the market without giving away the paid capability. We built free and premium apps from one codebase, with user management behind Azure AD B2C and digital torque readings in the premium tier.

500%Rise in potential clients after launch
IoT Core Engine self hosted platform built by Dev Station
Case study, IoT platform

A platform the customer owns outright

IoT Workz was locked into a SaaS vendor with no white labelling. We built a self-hosted platform on ThingsBoard with a white-label layer, Keycloak sign-on, a rule engine and multi-tenant isolation.

100%Platform ownership, no vendor lock-in

Tell us what you are selling

Three fields. An engineer reads it, and you get an answer within one working day.

  • We map tenants, tiers and how it gets delivered
  • You get an architecture sketch and a cost band
  • No obligation, and no phone number needed to start
FAQs

Questions we get on the first call

Should we start with an MVP?

Start with the smallest thing one real customer would pay for. That is usually narrower than an MVP as normally scoped, and it tells you more.

Multi-tenant or one deployment per customer?

Multi-tenant unless buyers demand their own instance. We have built both, including a platform designed to be self-hosted by the customer.

Can you build the free tier and the paid tier from one codebase?

Yes, and that is how the Hydrajaws apps work. Entitlements are enforced server side, so paid features cannot be switched on from the device.

Do you handle billing?

We integrate the billing provider you choose and enforce entitlements against it. We do not build payment processing from scratch.

Bring the pricing model with the feature list

How you plan to charge tells us more about the build than a backlog does. Thirty minutes and you will have an architecture sketch.

Let's Talk