Between systems
Services that sit between the platforms you already run. Handoffs that used to wait for someone to notice now move on every event, with retries and an audit trail.
Landvex is a founder-led engineering company in Stockholm and Houston. The platforms you already run each do their job — we build what sits in between: the handoffs, the exceptions, and the data that never quite lines up.
Six things we are asked for. In practice they arrive mixed together: a document pipeline that has to write into an ERP, a model whose output somebody has to be able to defend, a data layer nobody can trace. We build the whole path — including the unglamorous end of it, where the handoffs, retries and audit trails live.
Services that sit between the platforms you already run. Handoffs that used to wait for someone to notice now move on every event, with retries and an audit trail.
Extraction, classification and validation of documents, images and video at volume. Confidence scored per field, with exceptions routed to a reviewer instead of the whole batch.
Model orchestration with evaluation harnesses, guardrails and cost ceilings. We treat inference as a line item, not a demo.
Ingest, storage and query layers built so every number can be traced back to its source. Lineage is a requirement, not a report generated afterwards.
Accounts, IAM, networking and infrastructure as code — built in your cloud account, under your billing. EU and US data residency is set at the account boundary.
We build, you run. Most of what we ship carries your name, in your accounts. Delivery is the code, the infrastructure as code and the handover — not an operations contract.
The people who scope your work are the people who build it. There is no account layer between you and the engineers, and the engagement ends with a system you own rather than a retainer.
Two or three days with the people in the middle. We map what the large systems do not cover — volume, handling time, error rate — before proposing anything.
A narrow slice in production within weeks, running alongside how the work is done today so the two can be compared directly.
Widen the scope only where accuracy and cost hold up. Everything is infrastructure as code from the first commit.
The system ships as yours, under your name where that is the deal. Runbooks, dashboards and the code go with it. We do not stay on as an operations team.
We build products for our own companies, and sell most of them on to the organisations that need them most — under their name, in their accounts. Alongside that we take two to five project assignments a year.
We are a development company. We do not offer operations.
We build products for our own companies. That is where most of the year goes, and it is where the engineering standard is set.
Most of those systems we sell on to the organisations that need them most. Your brand, your accounts, your operations.
Two to five project engagements a year. Founder-led from the first call, chosen because the problem sits in a gap we know how to close.
We design and build. We do not sell on-call, staffing or managed operations. When the work is done, the system is yours to run.
Stockholm covers the European day and EU data residency. Houston covers US Central and the North American entity. The overlap is deliberate — most days both offices are online together.
Landvex AB · Antennvägen 2, 135 48 Tyresö, Sweden · Org.nr 559141-7042. European engineering, EU regulatory work, and data kept in region.
Landvex Inc. · Houston, Texas. The US headquarters, and where North American work is contracted and built.
Senior engineers only. Two to five assignments a year, so the ones we take get the whole team rather than a slice of it.
Accuracy, throughput and cost are measured against how the work runs today, and reported as they are.
White label by default. Code in your accounts, infrastructure as code, no proprietary lock-in and no operations contract attached.
License a system we have already built, or bring us a gap between the platforms you run. Either way, describe the work as it happens today — who does it, how often, and what goes wrong. You will hear back from a founder, not a form.