Repository navigation
chore: add Weik.io to the commercial products built on Apache Camel - #1858
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Weik.io by Adafy Oy (Finland) to the commercial products table on the user stories page.
Weik.io runs integrations as Apache Camel routes (YAML, XML or Java DSL). Each integration pins its own Camel version, currently 4.18.5 or 4.22.1, and runs in its own JVM. Locally, routes run with Camel JBang. Self-hosting is free, and Weik.io Cloud and Weik.io Dedicated are paid offerings.
It is listed under commercial products rather than open source projects. Weik.io describes itself as Apache 2.0 licensed, but its GitHub repository (weikio/weikio) contains no platform source code, only docs, examples and schemas.
🤖 Generated with Claude Code