diff --git a/src/components/sections/WhyUs.astro b/src/components/sections/WhyUs.astro new file mode 100644 index 0000000..fbfd96a --- /dev/null +++ b/src/components/sections/WhyUs.astro @@ -0,0 +1,34 @@ +--- +// Final nJAMS-legacy wording is subject to Hendrik's trademark review before go-live +// (see docs/superpowers/specs/2026-04-24-cameleer-website-design.md §10). +--- +
+
+
+

Why Cameleer

+

+ A purpose-built tool, from the team that has built integration observability before. +

+
+
+
+

Generic APMs do not understand Camel. Cameleer does.

+

+ Our Java agent speaks 45+ Apache Camel EIP node types natively — choices, splits, multicasts, doTry, error handlers, dynamic endpoints, thread boundaries in async routes. It extracts your route topology as a first-class graph, not a pile of metrics. +

+

+ A bidirectional protocol lets the server push deep-trace requests, per-route recording toggles, and signed config changes back to running agents — turning passive observability into active control. Not something you build in a weekend. +

+
+
+

Built by people who have shipped this class of product before.

+

+ The Cameleer team spent years building and supporting integration monitoring for banks, insurers, and logistics operators. We know what integration teams actually need at 3 AM — and what they never use. +

+

+ Cameleer is what we would build today, purpose-built for Apache Camel — no legacy, no retrofit, no assumptions about a generic middleware platform. +

+
+
+
+