Draft:Angry Monkey Ltd
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|
| Type | Private company |
|---|---|
| Industry | Software |
| Headquarters | United Kingdom |
Area served | Worldwide |
| Products | RouteBlaze |
| Website | routeblaze |
Angry Monkey Ltd is a United Kingdom–based software company that develops enterprise integration and lifecycle management platforms. The company is best known for RouteBlaze, a commercial platform designed to manage and orchestrate containerised Apache Camel runtimes in distributed environments.[1][2]
Angry Monkey Ltd primarily serves organisations with complex integration requirements, including those operating in regulated industries such as financial services and banking.
History
[edit]Angry Monkey Ltd was founded in the United Kingdom to address operational challenges associated with large-scale enterprise integration systems. The company focused on building tooling around open-source integration frameworks, particularly Apache Camel, to improve lifecycle management and governance across distributed environments.[3]
RouteBlaze
[edit]Overview
[edit]RouteBlaze is a commercial software platform developed by Angry Monkey Ltd for managing the lifecycle of containerised integration runtimes built on Apache Camel. The platform is designed to support deployment, orchestration, and operational governance across multiple servers and environments.
Architecture
[edit]RouteBlaze uses a distributed architecture composed of several core components:
- Camel Cores – Containerised Apache Camel runtimes that execute integration routes.
- Node Managers – Per-server management agents responsible for deploying, monitoring, and controlling local Camel cores.
- RouteBlaze Studio – A desktop application that provides visual lifecycle management, security configuration, and orchestration across multiple nodes.
This architecture enables centralised control while allowing runtimes to be deployed across geographically or logically distributed environments.
Features
[edit]Key features of RouteBlaze include:
- Centralised lifecycle management of distributed integration runtimes
- Role-based access control and security enforcement
- Visual orchestration and monitoring through a desktop management application
- Support for containerised and DevOps-oriented deployment models[4]
Business Model
[edit]Angry Monkey Ltd licenses RouteBlaze commercially to enterprise customers. Licensing typically includes access to updates, deployment rights, and support agreements.[5]
Industry Use
[edit]RouteBlaze is used in environments where integration governance, operational oversight, and deployment consistency are significant requirements, including regulated sectors such as banking and financial services.
See also
[edit]References
[edit]- ^ "RouteBlaze". barbuck.com. Retrieved 2026-01-27.
- ^ "Commercial Camel offerings". camel.apache.org. Apache Software Foundation. Retrieved 2026-01-27.
- ^ "Who we are". routeblaze.io. Retrieved 2026-01-27.
- ^ "RouteBlaze Reference Guide". routeblaze.io. Retrieved 2026-01-27.
- ^ "Commercial Camel offerings". camel.apache.org. Apache Software Foundation. Retrieved 2026-01-27.

- provide significant coverage: discuss the subject in detail, excluding routine coverage like product launches, staff appointments, or financial reports and listings in databases or listicles;
- are reliable: from reputable outlets with editorial oversight;
- are independent: not connected to the subject, such as press releases, the subject's own website, or sponsored content.
Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia.