Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions content/community/user-stories.md
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,7 @@ Several commercial software products and platforms use Apache Camel as their cor
|[Smile CDR](https://smilecdr.com/docs/camel/)|FHIR-native clinical data repository by [Smile Digital Health](https://www.smiledigitalhealth.com/) (Toronto, Canada), built on HAPI FHIR, which Smile maintains. Its Camel module runs Apache Camel 4.18 and lets customers write their own routes in YAML or XML DSL, with a dedicated `smile:` component for Smile CDR processors and broker ingestion from Kafka, ActiveMQ, and Pulsar. Used in 190+ implementations, including 30+ US healthcare payer deployments.|
|[Aiden Connect](https://aiden.eu/en/portfolio/add-ons/aiden-solutions/aiden-connect/)|Integration platform by [Aiden](https://aiden.eu/), offered as a managed service, that connects ERP systems such as SAP Business One, SAP Business ByDesign, and SAP Cloud ERP with webshops, logistics systems, and cloud applications. It runs as microservices on Google Cloud with data stored only in the EU. Aiden describes it as "our own integration platform, built on Apache Camel" and is developing it into a hyperautomation platform with visual integration routes and AI ([vacancy](https://aiden.eu/over-aiden/werken-bij/integratie-consultant-aiden-connect/)).|
|[Lunex](https://etzel.com.tr/en/products/lunex/)|Integration platform by Etzel, built on Apache Camel, that connects shop-floor systems (OPC UA, MQTT, PLC4X, MTConnect) with SAP (RFC/BAPI) and enterprise applications. AI agents write and test routes over MCP, using Lunex's tools and the Camel MCP tools served by each project's development pod. A built-in AI assistant answers questions from live SAP and machine data by calling those routes as tools. Routes are Camel YAML kept in Git and run on Kubernetes on the customer's own infrastructure. Interactive demos: [automated warehouse with SAP EWM](https://etzel.com.tr/en/products/asrs-demo/) and [demo factory](https://etzel.com.tr/en/products/demo-factory/).|
|[Weik.io](https://weik.io/)|GitOps integration platform by Adafy Oy (Jyväskylä, Finland) that manages integrations, APIs, file transfers, and events. Integrations are [Apache Camel routes](https://weik.io/camel-integrations) in YAML, XML, or Java DSL that can use Camel components and Kamelets. Each integration pins its Camel version, so routes on different Camel releases run side by side on the same agents, each in its own JVM, and `weikio dev run` runs them locally with Camel JBang. Agents run on Linux and Windows Server, on-premises or in the cloud. Self-hosted for free, or as the paid Weik.io Cloud (hosted in Helsinki) and Weik.io Dedicated offerings. In production since 2018. [Live demo](https://demo.weik.io/).|
{{< /table >}}

## Open Source Projects Using Apache Camel
Expand Down
Loading