We build and operate our own products.
Alongside client work, Bitwater Labs develops its own software products and operates them under its own responsibility. This page explains how we approach that work. The products themselves will be presented here once they are publicly released.
How we approach our own products.
When we build for ourselves, we live with every decision long after it is made. Four commitments follow from that.
Long-term ownership
We build products we intend to maintain for years. That shapes decisions from the start: data models that can evolve, dependencies we can keep current and features we are prepared to support.
We operate what we build
Deployment, monitoring, backups, security updates and incident response are our job, not someone else’s. What we learn in operation flows back into how we build, for our products and for client projects.
Quality as the default
Tests, code review and documentation are part of every change, not a phase at the end. We would rather release less and release it well.
Privacy by design
Our products are designed to collect the data they need to work, and nothing more. Data flows are documented and access is kept narrow.
Shown here once they’re public.
We present a product on this page when it is publicly released, with an accurate description of what it does at that point. Until then, we don’t publish names, feature lists or dates. We would rather show working software than announce plans.
Product inquiries and technology partnerships.
If our product work is relevant to you, we’d like to hear about it.
Product inquiry
Have a question about our product work, or a problem you think a product of ours should solve? Tell us about your use case and requirements.
Send a product inquiryTechnology partnership
Building something where our engineering could complement yours, such as an integration, a shared platform or a joint product? Describe what you have in mind.
Propose a partnership
Looking for a product built for your own business? See SaaS & Product Engineering