Concept
Meridian
Web applicationAn operations platform concept for logistics teams who currently run scheduling across three spreadsheets and a group chat.
- Product strategy
- UX architecture
- Web application
- Backend
Engineering
Backends that stay correct under load and change.
Interfaces get the attention. The data model decides what the product can become.
Technology
- Node.js
- PostgreSQL
- Redis
- REST and GraphQL
- Docker
- Cloud platforms
- Observability tooling
The problem
What usually goes wrong
Backends accumulate. Endpoints get added for one screen, the schema drifts, and eventually nobody can answer a basic question about the data with confidence.
Integrations are written once, without retries or observability, and fail silently in production.
Our approach
What we do instead
We design the data model deliberately, keep the API surface intentional, and make failure states explicit.
Everything ships with monitoring, sensible logging and documentation — so the next engineer, including yours, can move safely.
Capabilities
Data modelling and schema design
REST and GraphQL API design
Authentication and authorisation
Third-party and legacy integration
Background jobs and queues
Caching and performance work
Database migration and optimisation
Monitoring, logging and alerting
Security hardening
Deliverables
What you actually receive.
Scoped per engagement — this is the shape of it, not a fixed package.
01Data model and schema
02Documented API
03Service implementation and deployment
04Integration layer with retry and failure handling
05Monitoring and alerting setup
06Technical documentation
Process
How this work runs.
Six stages, adapted to the shape of this particular engagement.
01
Discover
Understand the business, the users and the constraint that actually matters.
02
Define
Turn ambiguity into a scoped direction — what gets built, and what does not.
03
Design
Structure the experience, then the interface and the visual system.
04
Build
Engineer the product, its integrations and its content model.
05
Launch
Deploy, instrument, test against real usage.
06
Evolve
Measure, improve and extend once reality has an opinion.
Related work
Where this shows up.
Internal concepts and prototypes that exercise this capability. Labelled, because they are not client engagements.
Yes. We audit first and work incrementally rather than proposing a rewrite by default.
Yes, including live migrations with rollback plans.
Related capabilities
Next step
Backend holding the product back?
Tell us the situation in a couple of sentences. We will come back with what we would do first, and whether we are the right people for it.