If you've ever worked in a large company, you've probably encountered "shadow infrastructure": scripts nobody understands or custom connectors written once and never touched again. This glue layer isn't documented, isn't owned by anyone, and tends to break when systems are upgraded or someone leaves. It's also the part everybody dreads working on, because it's hard to understand, painful to work with, and full of unknown unknowns. We built superglue so that engineers stop wasting time on deciphering legacy APIs and documentation. superglue ingests existing glue code, SQL, configs, docs, OpenAPI specs and reverse-engineers what the system is actually doing. It then maps dependencies and regenerates everything as clean javascript code that can run directly or be exposed via MCP or SDK. It also monitors API changes and schema drift, and automatically repairs integrations when upstream systems change. In short: It turns legacy integrations into code you can easily understand, test, and update. So that engineers can do more exciting feature work, and companies can migrate and upgrade systems faster. Think of it as: a context engine + code generator + integration runtime for legacy glue. What we'd love feedback on - How do you deal with "nobody knows what this script does" situations? - What would you want to know about your legacy systems? OSS/community version: https://github.com/superglue-ai/superglue More info: https://superglue.ai Happy to go deeper on the technical details. |