Come aboard
Whether you want to ship code, chat in real time, ask a quiet question, or reach out about a commercial engagement — here is every way to get in touch with the Bowire crew.
Why it’s worth being on deck
What you get out of actually being part of the crew — not just a GitHub star in a pile.
-
Your input moves the roadmap.
Bowire is small enough that a protocol gap flagged in Discord can land in the next review — not in six months.
-
Bugs get a human reply.
No auto-responses, no template close. Open an issue and somebody on the crew actually reads it.
-
Contributors are named.
Every release credits the people who shipped the fixes and features inside it — whether that’s one line of CSS or a whole protocol plugin.
Where the crew hangs out
Three places, all on GitHub. Contribute work, keep an ear to the rigging, or ask a question.
Report a bug, propose a feature, or send a pull request. The contributor guide covers the dev setup and coding conventions.
Star the repo to bookmark it, watch releases for version drops, or follow the roadmap to see what's in the pipeline.
Real-time chat with the crew. Bowire lives on the shared Küstenlogik server alongside Surgewave and the other coast-side dev tools — pick the channel that matches what you came for and you'll land in it the moment you join.
Prefer async over chat? Open a GitHub Discussion, or file a question-labelled issue if Discussions aren't enabled yet.
Activity on deck
Who’s aboard right now, and what the crew has been shipping. The cadence is small but real — the “last release” line below is the honest signal.
What’s recently shipped
All releases →- Releases (30d)
- 1
- Last release
- 13 d ago
- Last push
- 3 h ago
-
Packages that no longer bring a known advisory with them — A security patch for 2.9.0. Several published packages pulled dependencies with known advisories into every project that referenced them — the OpenAPI adapters a YAML reader open to a denial of service, the OIDC…
-
A Bowire that works behind the corporate proxy, signs in the Windows way, and keeps its cookies — 2.9 is the release for the network a company actually has. Bowire gets out through a mandatory proxy and trusts the CA a TLS-inspecting proxy signs with, calls intranet APIs as the signed-in Windows account, and…
-
Credentials that left through the wrong door, and a locked URL that was not locked — A security patch for 2.8.0. Three defects exposed credentials or the network behind a Bowire: internal plugin configuration — private keys and secret keys among it — went to the target as request headers, history and…
-
A workbench in two languages and several panes, a test pillar that reaches CI, and a Bowire that knows the others — 2.8 is the release in which the workbench stops assuming one of everything: one language, one live method, one Bowire. It speaks German and English throughout, holds two methods open side by side, and one Bowire can…
Drop us a line
For anything that doesn't fit into a public issue — commercial support, custom protocol plugins, partnership inquiries, or a quiet question — reach out directly.
Commercial & partnerships
Bowire is designed and maintained by Küstenlogik, a software studio in Northern Germany building distributed-system tooling. We also offer commercial support, custom protocol plugins, and integration help for teams running Bowire in production.
- Email info@kuestenlogik.com
- Web kuestenlogik.com
- GitHub @Kuestenlogik
Share your log
How is Bowire helping your team? What broke, what clicked, what edge cases you hit? Stories show up in release notes and shape what we prioritise next.
Add a log entry
Open a GitHub Discussion with your story — a paragraph, a screenshot, a “this saved my day”. The good, the bad, the edge cases. Every entry informs what we pick up next.
New entry →Read the logbook
Browse what the crew has shared so far. If another voyage matches yours, chime in — the thread is better with more voices.
Browse voyages →Every star is a small vote of confidence. Adds up. Adds weight. Adds yours?
Star on GitHub