Show HN: Ductape – Build back end integrations once, reuse them anywhere
29 Ifedayo_s 19 5/5/2025, 8:04:23 AM ductape.app ↗
Hey HN,
We built Ductape to make backend integrations reusable and environment-agnostic.
You define the logic once (e.g. payments, auth, notifications) and externalize provider-specific stuff like API keys, endpoints, and retries into a config.
That logic can then be reused across services, projects, and environments without rewriting code.
It’s like decoupling your service logic from your infrastructure. You can even switch providers by changing config, not code.
We’re using it to save time, reduce bugs, and simplify service expansion. Curious what you think.
We’ve been building quietly and are now coming out of stealth with our public beta. We’d love your feedback
You can try it at www.ductape.app
Join our Discord — https://discord.gg/JHXxQ6MAwb We’re there to chat, answer questions.
Happy to answer anything below..
They all have to handle authentication, retries, error handling, and webhook processing separately. You have to manually configure and update and test across envs.
So if you want to make a change, you'll have to go into each service and rework the integration logic.
With Ductape, instead of embedding provider-specific logic in every service, you write it once and configuration files handle the differences between environments and providers. So you can use same logic across your billing, subscription, and checkout services without duplication.
If you want to switch providers, you don’t touch the logic at all. You just update the configuration.
It would be great to have a simple example or a scenario or a hello world for someone to say “Aha! I get what it is and how it can help me”
Its under the elastic license...
can you please tell me if this license bad or good in terms of open sourced-ness and where does it really fall on the spectrum.
Maybe I didn't see it and it is there (there is a Lot of text), but I think having the npm and Frontpage should link to a directory of actual, full examples would be good.
https://www.ductape.app/use-cases
Can you explain what you mean by opinionated? We've tried to make this as flexible as possible
For example instead of putting Braintree or stripe code in every service, you write one chargeCustomer() function in Ductape and call it from anywhere. If you want to switch to another provider, you just change a config file, not your code.
Just my 2 cents.