What we do

We build the systems that carry your success.

Four capabilities, senior engineers only, and a delivery team that has sat in your chair. Most of our work starts with a system that is holding a business back and ends with a solution that does not.

Talk to us See the work
AI Engineering Cloud Native Engineering Composable Commerce Data Engineering
Brighting engineers at work in Novi Sad
Sound familiar

What usually brings people here

01

The platform can't take the next step

It works, but every change is expensive and every release is a risk. The roadmap is now shaped by what the architecture allows.

02

The team is good but stretched

Not a headcount problem. A depth problem. Nobody has the room to own the hard part properly.

03

AI is a pilot, not a capability

Demos land. Nothing reaches production because governance, evaluation and ownership were never designed in.

Capability

AI Engineering

Agents that run in production, with the governance, evaluation and observability that lets you put them in front of customers.

Agentic architecture

Agent discovery, autonomy boundaries, memory, tool access. Designed against a 42-capability maturity model, not a demo.

Trust at scale

Automated evals, human-in-the-loop where it matters, policy enforcement across providers.

Platform assessment

Two weeks. Where your architecture actually stands and what to fix first.

Build and run

From MVP to managed service, without model or region lock-in.

MCPBedrockAWSPythonLLM evals
ASICS · AI Engineering

Full readiness assessment for AI scalability across 42 capabilities

42 capabilities scored across discoverability, autonomy, intelligence and trust
Read the case →
Brighting engineers at work in the Novi Sad office
Our product

Agentic AI Platform

Build and run agents with no model, region or vendor lock-in. Agent portal, governance, observability, deployed in two weeks. Managed if you want it.

See the platform Get the whitepaper
Brighting engineers at work in the office
Capability

Cloud Native Engineering

Serverless systems, integrations and platform work that hold up under peak and stay cheap to change.

Product builds

API-first services from empty repo to live, typically inside four months.

Integration and automation

The unglamorous middle: ERP, OMS, carriers, legacy platforms, made reliable.

Platform modernisation

Incremental migration off the parts that are slowing releases down. No big bang.

Run and support

Monitoring, incident response, SLA. 365 days a year where the business needs it.

AWS LambdaCDKEventBridgePythonJava / SpringTerraform
Milence · Cloud Native Engineering

The first reservation system for European truck charging

4 months from empty repo to a standard adopted across the ecosystem
Read the case →
Capability

Composable Commerce

Commerce architecture for retailers and brands who need the flexibility without the re-platforming.

Architecture and selection

Which pieces to compose and which to leave alone. Vendor-neutral, because we are not reselling anyone.

Omnichannel fulfilment

Real-time stock, ship-from-store, in-store picking, carrier orchestration.

Store systems

Electronic shelf labels, in-store apps, pricing at scale across hundreds of locations.

Migration

Off the monolith in stages, with trading continuity as the constraint.

CommercetoolsScayleContentstackSAPAWS
HEMA · Composable Commerce

Real-time pricing across 800+ stores

800+ stores live on electronic shelf labels, manual price updates gone
Read the case →
A shopper inside a HEMA store — omnichannel retail
The Brighting team in the Novi Sad office
Capability

Data Engineering

The layer underneath the other three. Pipelines that make operational data trustworthy enough to decide on.

Operational pipelines

Near real-time ETL across stock, promotions and channels. Cloud-native, not a warehouse project.

Asset and config data

Automated collection across cloud providers into one dependable source, audit included.

Simulation and planning

Modelling that turns operational data into a decision, not a dashboard.

DataBricksPythonAWS GluePostgres
HEMA · Data Engineering

One pipeline behind every stock number the customer sees

< 60s to reconcile stock across web, app and 800+ stores
Read the case →
Results focused approach

How we work

One method across all four capabilities.

01
1–2 weeks

Understand the constraint

We look at the system and the business around it. Usually the stated problem is not the constraint.

02
days

Agree the outcome

Written down, measurable, with the tradeoffs on the table. If we think you are buying the wrong thing we say so.

03
ongoing

Build with your team

Senior engineers inside your process, not a black box across a wall. Your repo, your standards, your IP.

04
from day one

Hand over or keep running it

Documentation and ownership transfer are part of the work. Managed service only if you want it.

Engagement models

Four ways to work with us

Product build

Fixed outcome, our team, our accountability. Typically 3–6 months.

Team augmentation

Senior engineers embedded in your team. No rotation surprises.

Advisory

Architecture and assessment work with a partner or fractional CTO, weeks not quarters.

Managed service

We run what we built. Monitoring, incident response, SLA.

The work behind it

All cases →
Cloud Native · EV infrastructure

Guaranteed charging slots for European truck fleets

4-month build, adopted across the ecosystem
Cloud Native · Beauty SaaS

POS fiscal compliance shipped inside the regulatory window

~2,000 partners unblocked
Composable · Retail

Real-time pricing across 800+ stores

Manual price updates eliminated

The questions we always get

Because the rate is not the argument. Novi Sad is where we found engineers who stay, go deep, and take ownership. Delivery, strategy and product sit in Amsterdam, in your timezone, and the team you meet is the team that builds.

Seniority is not just experience or age count. It is about understanding the problem, proposing the right solution and being able to execute against it. You meet the engineers before you sign, they are named in the proposal, and if someone has to change we tell you why before it happens.

It is yours throughout. Your repository, your cloud account, your IP, documented as we go rather than in a handover week at the end. Leaving cleanly is part of the engagement, not a penalty clause.

We add people at the pace we can keep the bar, which is roughly one engineer a month onto a running team. If you need thirty next quarter we are the wrong partner, and we will say so in the first conversation.

We are deepest on AWS and hold the Retail Competency there, but we resell nothing and take no vendor margin. On commerce platforms we have built on several and will recommend the one that fits, including the one you already own.

Have a system that is holding you back?

Send us the shape of the problem. You will get a straight answer about whether we are the right people for it, including when we are not.

+31 20 210 13 90 info@brighting.nl Grasweg 183, 1031 HX Amsterdam