Customer and partner portals
Sign-in, roles, invitations, per-account data and the screens each persona needs. Exactly what this site's brand, distributor and partner portals are.
DEV SOLUTIONS · WEB
Web application development.
Portals, dashboards, marketplaces and internal tools: software that has logins, roles, data and real users. We build it the way we built this platform — one clear application, one database, tests that run before anything ships, and documentation that lets your team take it over.
WHAT WE BUILD
The applications businesses actually run on.
Dashboards and reporting
The numbers your team asks for, computed once on the server and shown the same way to everyone — with the filters and exports that make them usable.
Marketplaces and directories
Public, searchable listings with categories, structured data, shareable URLs and an admin who can publish and unpublish without a deploy.
Internal tools and workflows
Approvals, order flows, stock views and the small systems an operation depends on — usually the highest-value thing a business can fix.
APIs and integrations
REST endpoints, webhooks and connectors between your ERP, storefront, CRM and payment provider, with retries and logs so failures are visible.
Existing apps, rescued
Audit, stabilise and extend a web application someone else built. We start with what it would cost to fix versus replace, and say which we would do.
WHAT YOU GET
Every web project ships with:
- Working software per slice — a staging URL you can use, not a slide about it.
- Automated checks — the flows that matter are tested against a real database on every change.
- Reviewed code — no change reaches your main branch without a second engineer reading it.
- A documented deployment — the same repeatable step every time, and how to roll it back.
- The data model — written down, because it outlives the team that designed it.
- Your repository — code you own, in your account, from the first slice.
HOW WE BUILD
Boring technology, on purpose.
A web application is a long-term liability as much as an asset. We choose tools that are widely documented, easy to hire for and still supported in five years, then use them well:
Application
Python with Flask for the server, server-rendered pages with progressive JavaScript for the interface. One application serving every portal, rather than five deployments to keep in step.
Data
PostgreSQL or MongoDB depending on the shape of the data, with the schema and indexes written down and migrations treated as code.
Interface
Semantic HTML, a small hand-written stylesheet and JavaScript that enhances the page rather than being required for it — so a slow connection degrades instead of breaking.
Operations
Docker, one process to deploy, environment settings kept out of the code, health checks, error reporting and log access for the people on call.
ENGAGEMENT
Three ways to work with us.
Fixed-scope project
A written scope and a fixed price for a defined piece of software. Best when the requirement is clear and the deadline matters.
Dedicated squad
One or more engineers on your project a month at a time, working through a backlog you can see. Best when the product will keep changing.
Audit and rescue
A fixed-fee look at an application you already have: what it would take to fix, extend or replace, with an estimate rather than an opinion.
QUESTIONS
Web application development, answered.
What technology do you build web applications with?
Server-rendered Python (Flask) with progressive JavaScript for the interface, MongoDB or PostgreSQL for data, and Docker for deployment. We pick boring, well-documented tools on purpose: they are cheaper to hire for and cheaper to keep running than a bespoke stack.
Can you take over an existing web application?
Yes. It starts with a short audit of the code, the database and the deployment, and ends with a written estimate of what it costs to fix, extend or replace. If the honest answer is replace, we will say so.
How do you stop a web project from drifting?
Short delivery slices, a written backlog, and one point of contact. You see working software every slice rather than a status report, so scope changes are decisions with a price attached, not surprises at the end.
Will we be able to run it without you?
That is the goal. Handover includes the repository, the deployment steps, environment settings, the data model and a walkthrough with your team. Support afterwards is optional, not a requirement.
Bring us the web application you have been putting off.
Tell us who uses it and what it must do. We will reply with a scope, a first-slice price and a date — or an honest "not us" if it is the wrong fit.