A licensed integration platform, in two halves.
Interlock Studio is where an integration is discovered, built, and tested. Interlock Connect is the connector library it produces, running on whatever contemporary Java backbone you already operate. License either. License both. Run them with your engineers or ours.
Most integration tooling forces one purchase: adopt the vendor’s runtime and you get their tooling, or adopt their tooling and you inherit their runtime. Interlock separates the two deliberately.
Studio is a workbench - discovery, development, and test. It produces artifacts, not lock-in. Connect is 35 maintained connectors written against a thin adapter interface, so they deploy onto the Java backbone your platform team has already standardised on.
Discovery, development, and testing in one workbench - so the integration is specified before it is written.
AI sits in exactly two places inside Studio: carrying out system integration discovery, and defining the inputs connectors run against. Every output is reviewed and signed off by an engineer before it reaches a build. What Studio does not do is write your integration for you - that is precisely the claim you should distrust.
Interlock Connect
Connectors written against a thin adapter interface rather than a proprietary runtime. Each one handles the unglamorous part - authentication, pagination, rate limits, retry semantics, idempotency, error taxonomy - and deploys onto the backbone you already run.
Runtime-neutral by design
Certified against Apache Camel, Spring Integration and plain Spring Boot, Quarkus, and Jakarta EE application servers, on JDK 17 and above. A connector is a library on your classpath, not an appliance in your network.
Your deployment topology
Run them in-process inside an existing service, as standalone microservices, or as sidecars in your cluster. Interlock has no opinion about your orchestration and does not require an eProxim-hosted control plane.
Maintained against upstream drift
When a vendor deprecates an API version or changes a schema, the connector is updated and released. That maintenance is the substance of the subscription - the code you already have keeps working.
Source-available under licence
Licensees receive source. Your team can read it, debug it, and patch it in an emergency without waiting on us. Nothing about Interlock stops you operating what you have bought.
The connector library
35 systems, honestly labelled. Some are generally available and have carried production traffic for years; some sit in the library awaiting their first client environment; some we build to order and then maintain like the rest.
Not listed is not a problem. Anything with an API, a message broker, a database, a file drop, or an EDI feed is in scope - the list reflects what has come up most, not the limit of what we connect. Commissioned connectors are quoted per system and maintained on the same terms as the rest of the library.
How it is licensed
Annual subscription, priced on environments and connectors rather than seats or message volume. No per-transaction metering.