01
Durable work
Work Items, attempts, leases, retries and milestones live in SQL Server rather than disappearing into process memory.
Technical preview in development
Reliable data flows.
Visible business.
Vuo is a durable integration platform for teams that want ordinary C#, understandable SQL state, safe retries, and clear answers when something fails.
SQL-backed work
Ordinary C# processors
No broker required
vuo work show 184293
FLOWCustomer A — DESADV
STATEFAILED
STEP3 — HTTP delivery
FAILUREAccessDenied
INPUTDESADV_12345.edi
The ERP API rejected the configured credentials.
View inputTest processorRetry
Business health
A technically healthy integration can still be a business failure.
Services may be running, no exceptions may be logged, and every technical health check may be green — while an expected order, shipment, file, or acknowledgement never arrived.
Vuo can evaluate what the business expected to happen, not only whether the software itself reported an error.
Technical health
Healthy
Errors
None
Business health
Critical
Reason
Customer A: Expected DESADV file has not arrived by 10:00am.
What Vuo is for
Integration operations without the archaeology.
When an integration misbehaves, the system should tell you what it was doing, what already succeeded, what failed, and what happens next.
02
Useful failures
See InputTruncated in “Parse DESADV”, not only a stack trace several layers below the business problem.
03
Exact evidence
Keep the exact input bytes that failed, with hash and provenance, so investigation does not begin with hunting through file shares.
04
Self-protection
Volume, storage and processor guards are designed to slow down, isolate and explain abnormal conditions instead of amplifying them.
The operating model
Make the important state explicit.
Vuo separates business work from transport mechanics. A Flow creates durable Work Items, processors transform artifacts, Vuo owns delivery and recovery, and acknowledgement can remain visible for as long as necessary.
Walk through the lifecycle →01DiscoverSource or schedule
→
02ProcessOrdinary C#
→
03DeliverVerified output
→
04AcknowledgeBusiness completion
Built for developers too
Bring C#. Keep control.
Vuo is not trying to replace code with a proprietary visual language. Custom processors use a small SDK while the platform owns the dangerous operational edges around them.
Developer featuresCustom processor
await using IProcessorStep step = await context.Steps.BeginAsync(
"transform",
"Transform shipment",
cancellationToken);
ProcessShipment(input, output);
step.Complete();
Deliberate boundaries
What Vuo Platform is not
Vuo is intentionally focused. It is not trying to become every kind of integration, messaging, workflow, or infrastructure platform.
Not an Enterprise Service Bus
Vuo does not try to recreate every ESB pattern, messaging abstraction, or distributed integration feature. Its focus is durable, observable business data flows with explicit operational state.
Not Kafka
Vuo is not designed for massive event-stream processing or as a distributed append-only log. It is aimed at workloads where individual pieces of business work need to be understandable and recoverable.
Not a low-code transformation designer
Vuo does not introduce a proprietary visual programming language. When transformation logic needs code, Vuo expects ordinary C# that developers can test, review, version, and maintain normally.
Not Kubernetes-first infrastructure
Vuo is intended to run comfortably in conventional Windows and SQL Server environments. Containers and more complex deployment models should be optional, not prerequisites.
These boundaries let Vuo concentrate on durable Work Items, safe retries, artifact processing, business-level health, understandable SQL state, and reliable custom C# execution.
Early technical preview
Running file-heavy integrations on Windows or .NET?
Vuo is being built in public enough to learn from people who have the same operational problems. Tell us what hurts today.