Growbase
We build developer infrastructure and focused tools. Each one started as something our own products needed, ran in production, and then became a product of its own.
Products
Two are live today and running behind our own apps. Two are on the way. All of them are built to be understood, not just used.
Realtime chat for your app.
Server-authoritative messaging over a single WebSocket. Optimistic send, reconnect, backfill and unread counts are handled for you. Your app keeps identity, membership and paywalls. yappr keeps the messages.
Video infrastructure you host.
Resumable upload, adaptive transcode and HLS delivery with signed playback URLs. Bytes go straight to your own storage and never through our compute.
Approval-first customer support.
A support workspace where the AI drafts privately and proposes, and a person approves every customer reply and every reusable rule before it takes effect.
Product thinking, grounded in your code.
Capture an idea, get an assessment grounded in your linked repositories, discuss it, and record the decision with its reasoning so it survives the next session.
How we work
Nothing ships as a product until it has carried real traffic for one of our own apps. We find the sharp edges before you do.
HTTP you can call from any language, signed tokens instead of sessions, and documentation that describes the failure modes alongside the happy path.
Where AI is involved, it drafts and proposes. A person approves, decides, and owns the outcome. That is a design constraint, not a setting.
Contact
Integrating yappr or hostr, curious about duly or marinate, or want to compare notes on running small infrastructure well? Send an email and a person will reply.