Hey HN,
We built Ductape to make backend integrations reusable and environment-agnostic.<p>You define the logic once (e.g. payments, auth, notifications) and externalize provider-specific stuff like API keys, endpoints, and retries into a config.<p>That logic can then be reused across services, projects, and environments without rewriting code.<p>It’s like decoupling your service logic from your infrastructure.
You can even switch providers by changing config, not code.<p>We’re using it to save time, reduce bugs, and simplify service expansion.
Curious what you think.<p>We’ve been building quietly and are now coming out of stealth with our public beta.
We’d love your feedback<p>You can try it at www.ductape.app<p>Join our Discord — <a href="https://discord.gg/JHXxQ6MAwb" rel="nofollow">https://discord.gg/JHXxQ6MAwb</a>
We’re there to chat, answer questions.<p>Happy to answer anything below..
I also don't understand what your product actually does. What would help me: an example + diagram of a solution before and after the use of Ductape. How does this change things? The more detailed, the better (less marketing language, more example code / diagrams).
The concept of what you describe is interesting and useful. I struggle to make the same conclusion from the website, it feels like it is written as too abstract to allow the reader to grasp exactly what you will get. Was the text improved by an LLM?<p>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”
To the folks who are confused what this does, a very similar product with clearer positioning is <a href="https://nango.dev">https://nango.dev</a> (also a cool product and team I'd recommend)
All these integration/workflow products (Nango, Ductape, n8n, Camunda, etc) reminds me of SnapLogic, which have been there for years and years.<p>Just my 2 cents.
So this is like a bunch of patterns + implementation library of those patterns + PaaS runtime for that library? It is very hard to read this, but it seems it is similar to the library we use internally in our company to do this. Ours is very opinionated (this looks like this also) so we never thought of making it a product as it wouldn't fit in other companies, or so we figured.<p>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.