Custom boards
A workflow shaped exactly around your process — the columns, statuses, views, and rules your team actually needs, not the closest template.
Custom builds
If your process doesn't fit a template, we build the template.
Danube covers the way most teams work out of the box. When yours needs something off the standard path, we build it on the same platform — no separate tool, no bolt-on that breaks at the next update.
Built on the platform you already run — not bolted onto the side.
A custom build isn't a separate product held together with duct tape. It lives inside the same Danube your team uses every day, shares the same data, and keeps working when the platform updates. Your custom board talks to your standard ones; your custom automation fires on the same events. One system, extended — not two systems you have to keep in sync.
What we build
Three kinds of custom, one platform.
Most requests fall into one of these — and all three sit on top of the CRM or TMS you're already using.
Custom automations
The specific chain of triggers and actions your operation runs on — including logic no off-the-shelf recipe covers.
Custom integrations
A two-way connection to the tool nobody else integrates with — your ERP, a niche exchange, an in-house system.
How it works
From "can it do this?" to running in production.
- 1
We listen
You walk us through the workflow that doesn't fit. We map what you actually need, not what's easiest to build.
- 2
We scope
A clear proposal: what gets built, how long it takes, and what it costs — before any work starts.
- 3
We build
Developed on your platform, tested against your real data, reviewed with you as it takes shape.
- 4
We support
It ships, and it keeps working — maintained alongside the rest of Danube, not left to rot.
When it makes sense
Custom isn't for everyone — and that's the point.
Your process is genuinely different. Not "we'd prefer it blue" — a real workflow the standard product can't express.
You run a tool nobody integrates with. An ERP, a regional system, something in-house you can't leave behind.
The volume justifies it. The workflow runs often enough that automating it pays for building it.
You're on Enterprise, or heading there. Custom work pairs with the plan built for teams at scale.
Questions
What people ask about custom work.
How much does a custom build cost?
It depends entirely on scope, so there's no list price. You get a fixed proposal — what gets built, how long it takes, what it costs — before any work begins, so there are no surprises.
How long does it take?
A small custom board or automation can ship in days; a full integration with an in-house system takes longer. We put a realistic timeline in the proposal rather than promising a number we can't hold.
Do I need to be on a specific plan?
Custom work pairs naturally with Enterprise, since that's where the volume and the advanced features live. If you're not there yet, we'll tell you honestly whether custom is the right move or whether the standard product already covers it.
Will it break when Danube updates?
No. Custom work is built on the same platform and maintained alongside it — not bolted on the side where the next update knocks it over. It keeps working as the product evolves.
Can you integrate with our in-house system?
Usually, yes. If your system can talk to anything — an API, a database, a file export — we can build a two-way connection. Tell us what it is and we'll confirm before scoping.
What if I'm not sure it's really custom?
Then ask. A lot of what feels like it needs custom work is already possible in the standard product. We'd rather point you there than sell you a build you don't need.
Tell us the workflow that doesn't fit.
We'll tell you honestly whether it's a custom build or something the standard product already does — no upsell to work you don't need.