Production Support
24/7 incident response with an SLA. We pick up the pager when your cluster does. Triage, root-cause, fix, postmortem — all by the people who wrote the code paths.
We Wrote the Framework.
Surgewave is built and maintained by Küstenlogik. When you need production-grade Surgewave — performance tuning, custom plugins, Kafka migration, architecture review — talk to the people who wrote it.
Custom Plugins
Need a connector for an in-house system? A bespoke storage engine for your hot path? An AI pipeline node tied to your model registry? We build, sign, and ship it as a regular .swpkg.
Architecture Review
Pre-deployment audit before you put Surgewave on the critical path: capacity planning, replication topology, security review, failure-mode walkthrough. Two-week engagement, written report.
Migration & Training
Coming from Kafka, Redpanda, or a custom queue? We run the migration, train your platform team alongside, and stick around through the first week of production.
How an engagement works
1. Discovery call (free, 30 minutes)
We listen first. What is Surgewave doing for you, what is it about to do, and where is the risk? You leave the call with a written one-pager: scope, timeline, fixed-price or T&M shape, and a clear next step. No NDA pressure on this call — bring the architecture, leave the secrets at home.
2. Statement of work
Within five working days you have a signed-and-scoped SoW. Production support runs on a yearly retainer with a documented SLA. Custom plugins and reviews are fixed-price per deliverable. Migration & training engagements scale by cluster size and team count — ranges are public, no quotation lottery.
3. Delivery
We work in your repos and your incident-response channels. Every commit gets a postcard explanation in the PR description. Every architectural decision lands in an ADR you keep. When the engagement ends, your team owns everything — no consultancy lock-in, no opaque scripts, no "secret" plugins your engineers can't read.
4. Handover & tail
Two weeks of free post-engagement office hours after every fixed-price delivery so your team can ask the silly questions that always come up once the new code hits production. Anything beyond that rolls into the regular support retainer or stays one-off, your choice.
What we say no to
We don't take engagements where Surgewave isn't the right tool. If you should be running NATS, Redis Streams, or even plain Postgres LISTEN/NOTIFY, we'll tell you on the discovery call — usually in writing so you can take it to your leadership. Honesty here is cheaper than a six-month "Surgewave rollout" we both regret.
Who you'll work with
The same engineers who write the broker. No bench rotations, no offshoring the actual work. Küstenlogik is small on purpose; the people on the call are the people on the keyboard.