Skip to main contentKanal Landing Page Copy
HERO SECTION
Headline
Kafka streaming apps. Without the complexity.
Subheadline
Kanal is a visual builder that turns flowcharts into deployable containers. No Flink cluster. No platform bottleneck. Just your team, shipping real-time applications in hours instead of weeks.
Primary CTA
Request Early Access
Secondary CTA
Watch the 40-Second Demo
Product Visual
[Screenshot of visual canvas or embed demo video here]
THE PROBLEM
Section Headline
80% of your streaming apps look exactly the same.
Body
Consume from a topic. Look up reference data. Filter. Map. Upsert into a table.
That’s it. That’s the pattern.
And yet, shipping this simple pipeline requires weeks of boilerplate, rare expertise, and more Kafka concepts than anyone should need to learn.
Apache Kafka revolutionized how organizations think about data. It broke down silos. Gave teams ownership. Killed the middleware gatekeepers.
But somewhere along the way, it locked the development of streaming applications behind a wall of complexity.
For experts, by experts.
What the hell happened?
THE ALTERNATIVE ISN’T BETTER
Section Headline
Your options today? All of them hurt.
Body
Kafka Streams and Kafka Connect are two separate worlds.
One is a library. The other is a distributed runtime. Different APIs. Different paradigms. Different operational models. Both complicated. Both require specialists.
Want to consume, transform, and sink to a database? Congratulations—you’re now maintaining two technologies, each with its own learning curve and failure modes.
Centralized platforms make it worse.
Kafka succeeded because it removed coordination between application teams and platform teams. It cut out bottlenecks. Gave teams ownership. Killed the middleware gatekeepers.
Centralized streaming platforms reintroduce exactly what Kafka broke.
THE KANAL APPROACH
Section Headline
Boring by Design.
Body
I believe building real-time data pipelines should not feel like rocket science.
Kanal focuses on the boring 80% that everyone needs, not the shiny 20% that conferences celebrate.
Design your pipeline like a flowchart. Get a deployable container. Own your infrastructure. Ship.
No black boxes. No massive operational burden.
CORE BENEFITS
Benefit 1
From idea to production in hours, not weeks.
Visual design replaces framework plumbing. Serdes and schemas are there in the back serving your interests through autocomplete, hints, and various recommendations and guardrails.
Benefit 2
Deployment is a breeze.
One artifact. One Docker image. Owned by your team. No build.gradle, no pom.xml, just straight to your preferred orchestrator. Automated pipelines, environment management, health checks, and rollbacks included.
Benefit 3
The right monitoring, by default.
Real-time metrics. Actionable alerts. Performance insights. Prometheus endpoint ready. You shouldn’t have to build observability from scratch every time.
HOW IT WORKS
Section Headline
Four steps. That’s it.
Steps
-
Design your pipeline visually. Drag, drop, connect. Stream/table joins, transformations with JSONata, auto-complete guiding you through.
-
Generate a Docker image. No build.gradle, no pom.xml. Just a container ready for your orchestrator.
-
Deploy to your own infrastructure. Owned by your team. No shared cluster. No platform dependency.
-
Operate with built-in telemetry. Metrics, alerts, health checks, rollbacks, pause/resume, offset resets—all included.
FEATURES
Visual No-Code Design
Build pipelines the same way you’d explain them on a whiteboard. JSONata handles transformations. Auto-complete guides you through.
Decentralized Deployment
Ship a Docker image owned by your application team. No shared Flink cluster. No platform dependency. The autonomy Kafka promised, finally delivered.
Kafka Connect Plugin Compatibility
Drop any existing Sink Connector into a plugins folder. It just works. I built a decentralized Kafka Connect by accident—and it’s a feature, not a bug.
Batteries-Included Operations
Health checks. Metrics. Alerting. Rollbacks. Pause and resume. Offset resets. Everything you need to operate in production, without building it yourself.
SOCIAL PROOF
Section Headline
Built by someone who’s been in the trenches.
Body
15+ years in data integration. Kafka expert since 2018.
I’ve worked on both sides: Platform teams building tools, Application teams consuming them. That perspective taught me one thing: the best platform work is invisible. Low friction. High autonomy. Help teams ship. Don’t become another bottleneck.
I put that philosophy into practice: ns4kafka at Michelin for Kafka governance, then Conduktor where I rebuilt it as a product so more enterprises could benefit from this.
Every organization I’ve worked with faced the same problem: Kafka streaming requires skills that are hard to find, expensive to train, and frustrating to retain.
Kanal exists because I know these problems shouldn’t be this hard. The tools make it hard because they’re made by experts, for experts.
FINAL CTA
Section Headline
Ready to make Kafka streaming boring?
Body
I’m looking for enterprises to beta-test Kanal and provide feedback.
If this resonates, reach out. Let’s build something that actually helps.
Request Early Access
Kanal. Boring by Design. 
