# CodeBrewerz

> CodeBrewerz is a remote-first software studio: web, mobile and cloud products, AI features, QA and consulting. Hub in Pune, India; clients worldwide.

Contact: ceo@codebrewerz.com
Enquiries: https://codebrewerz.com/contact
Replies within one business day.

Published: 2026-08-14
Last updated: 2026-09-03
Author: Piyush Jain, CTO (https://codebrewerz.com/about)

## Services

Seven services delivered end to end, all of them remotely.

- **Web Development** - We design and build the website or web app your business runs on. Fast to load, easy to use on any device, and built to keep working as your traffic and your team grow.
- **Mobile Apps** - A mobile app your customers actually want to open, for iPhone, Android or both. Quick and natural to use, and built so new features arrive without a full rewrite.
- **UI/UX Design** - We map out how people will actually use your product, then design screens that make the right next step obvious. Less confusion for your users, fewer support tickets for you.
- **Cloud Solutions** - We set up the hosting and infrastructure behind your product so it stays up under real traffic, grows when you need it to, and takes new releases without downtime.
- **Quality Assurance** - Before anything reaches your customers we test it, by hand and with automated checks that keep running long after launch, so bugs get caught before they become support calls.
- **Consulting** - Not sure what to build first, or whether your current setup can carry you to the next stage? We'll look at where you are, where you're headed, and give you a clear, practical plan to get there.
- **Automations** - The repetitive parts of running your business, like data entry, reports and handoffs between tools, set up to run on their own. On a schedule or the moment something happens, with nobody watching.
- **Engineering Blog** - Notes from the team on how we build things and what we learn taking real systems apart. Written for anyone curious about what is going on under the hood, not only engineers.

## Products

Four products built and run in-house. Statuses are literal: three of the four are pre-launch and should not be described as available.

- **LogiHaul** (Live) - A logistics platform for fleets, covering trips, vehicles, drivers, companies and billing, with each company's data kept separate and secure. Drivers use a mobile app on the road while the office team manages the same information from a web dashboard. No more chasing paper trip sheets or reconciling spreadsheets at month-end. Stack: Fastify, PostgreSQL, Kysely, Expo, React.
- **unMail** (Alpha) - An email design and sending tool. Build templates with a simple drag-and-drop editor, connect the email service you already use, and send emails either from the dashboard or automatically through your own systems. No fighting with email HTML, and no lock-in to one sending provider. Stack: TanStack Start, Fastify, oRPC, Prisma, PostgreSQL.
- **Hivemind** (Alpha) - A team chat app with a built-in AI assistant that already knows what is in your other work tools (Jira, GitLab, GitHub, Bitbucket and Slack) and only shows people what they are allowed to see. Ask it a question and it answers from your actual tickets, code and conversations, not a generic guess. The architecture is finished and the build is underway. Stack: Fastify, Prisma, PostgreSQL, React 19, Expo.
- **Snugl** (Coming Soon) - A URL shortener built on a Rust API and SQLite, with a dashboard for creating and tracking links. Redirects are served from a dedicated short domain, kept apart from the dashboard and API for both security and speed, with click analytics, expiring and permanent links, and plan-based limits built in from the start. Stack: Rust, SQLite.

## Engagement model

CodeBrewerz works either as a fixed-scope project team or as an embedded team alongside your engineers. Consulting-only engagements are available. The four steps below run from a first message to a production-ready MVP.

1. **Send a brief** - Describe the project, the services you need and your preferred start date through the contact form on codebrewerz.com or by email to ceo@codebrewerz.com.
2. **Take a scoping call** - CodeBrewerz replies within one business day and books a scoping conversation to agree the problem, the constraints and the shape of the engagement: fixed-scope project team, embedded team, or consulting only.
3. **Run discovery and design** - Two to three weeks of discovery and design establish the architecture, the data model and the interface before any production code is written.
4. **Ship in two-week increments** - Delivery proceeds in two-week increments, each ending in a working build you can use, with a production-ready MVP typically landing eight to twelve weeks from kickoff.

## Automation templates

Six workflow files, MIT licensed and downloadable with no signup from https://codebrewerz.com/automations. Written against each tool's documented schema and checked to parse; not executed against a live instance.

- **Lead router** (n8n) - Contact-form submissions land in an inbox nobody owns, so the urgent ones wait behind the rest. Trigger: A POST to an n8n webhook from your contact form. Download: https://codebrewerz.com/automations/lead-router.json
- **Pipeline failure digest** (n8n) - CI notifications are either off, or so constant that nobody reads them. Trigger: A schedule, every weekday at 09:00. Download: https://codebrewerz.com/automations/pipeline-failure-digest.json
- **Nightly Postgres rollup** (Kestra) - Reporting queries run against the live orders table at whatever hour someone opens a dashboard. Trigger: A schedule, 02:00 UTC every night. Download: https://codebrewerz.com/automations/nightly_postgres_rollup.yaml
- **API uptime and latency check** (Kestra) - An endpoint degrades on a Friday evening and the first report comes from a customer on Monday. Trigger: A schedule, hourly. Download: https://codebrewerz.com/automations/api_uptime_and_latency_check.yaml
- **Daily metrics rollup** (Apache Airflow) - A reporting job written as a cron script has no retries, no history and no way to backfill a missed day. Trigger: A DAG schedule, 03:00 UTC daily. Download: https://codebrewerz.com/automations/daily_metrics_rollup.py
- **Regression suite and report** (Apache Airflow) - The full regression suite is too slow for every commit, so it stops running at all. Trigger: A DAG schedule, weekday mornings at 01:00 UTC. Download: https://codebrewerz.com/automations/regression_suite_and_report.py

## By the numbers

- 7: services delivered end to end.
- 4: products built and run in-house.
- 1: of those products in daily production use.
- 8-12 weeks: from kickoff to a production-ready mvp.
- 2-3 weeks: discovery and design before the first build.
- 2 weeks: delivery increment, each ending in a working build.
- 1 business day: typical time to a reply and a scoping call.
- 5: email providers unmail sends through.
- 6: automation templates, free to download.

## Standards the work is measured against

- According to the W3C Web Content Accessibility Guidelines 2.2 (https://www.w3.org/TR/WCAG22/), every interface CodeBrewerz ships is built to meet the AA conformance level: keyboard operable, contrast-checked, and readable by a screen reader.
- According to Google's Core Web Vitals thresholds (https://web.dev/articles/vitals/), a good page load means Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. CodeBrewerz treats those three thresholds as the performance budget for every front end it delivers.
- According to the OWASP Application Security Verification Standard (https://owasp.org/www-project-application-security-verification-standard/), authentication, session management and access control need verification rather than assumption. CodeBrewerz builds against that checklist. LogiHaul shipped with session-cookie auth, CSRF protection, Argon2id password hashing and per-tenant query scoping.

## Writing

The CodeBrewerz engineering blog lives at https://codebrewerz.com/blog. Posts are long-form explainers with interactive diagrams, written by Piyush Jain.

- [What Postgres Actually Does With Your Data](https://codebrewerz.com/blog/what-postgres-actually-does-with-your-data) - An UPDATE never touches your row in place, a COMMIT does not mean your data is on the heap file, and your index is sometimes ignored on purpose. Here is the machinery underneath all three. Published 2026-09-02.
- [Let's Build a Load Balancer From Scratch](https://codebrewerz.com/blog/lets-build-a-load-balancer) - Picking a backend is one line of code. Everything that makes a load balancer trustworthy — health checks, draining, hashing, backpressure — is the other ten thousand. Published 2026-08-31.
- [n8n vs. Kestra vs. Airflow: Picking an Orchestrator](https://codebrewerz.com/blog/n8n-vs-kestra-vs-airflow) - All three run steps in order and retry what fails. They were built for three different people — and that, not the feature list, decides which you run. Published 2026-08-29.
- [The Magic of WebSockets: How Your App Stays Live Without Asking](https://codebrewerz.com/blog/the-magic-of-websockets) - WebSockets replace "are we there yet" with a phone line that stays open. Here is the handshake, the framing, what HTTP/2 changed, and the limits you should know. Published 2026-08-29.
- [Let's Build a URL Shortener That Survives a Billion Links](https://codebrewerz.com/blog/lets-build-a-url-shortener) - A URL shortener is the smallest system that still has every hard problem in it — key generation, read/write asymmetry, caching, abuse. Here is the whole design. Published 2026-08-25.
- [What a CDN Actually Does (And When You Genuinely Don't Need One)](https://codebrewerz.com/blog/what-a-cdn-actually-does) - A CDN is not a speed setting. It is a cache on the network, here is what it caches, why distance costs milliseconds, and when a single origin cache is the better answer. Published 2026-08-23.
- [What Is Serverless, Really? The Honest Cost, Limits and Payoff](https://codebrewerz.com/blog/what-is-serverless-really) - Serverless is not "no servers". It is a usage based renting a system that bills on usage milliseconds rather than by the hours provisioned. Here are the pros and cons and hard limitations. Published 2026-08-23.

Scheduled, in order of publication:

- Let's Build a Secure Wallet: Keys, Signatures and Every Way It Leaks, 2026-09-05.
- Let's Build Tree-sitter: How Your Editor Parses Code On Every Keystroke, 2026-09-08.
- HTTP/3: What's New, and Where It Actually Earns Its Keep, 2026-09-11.
- WebSockets vs. Server-Sent Events: When to Use What, 2026-09-14.
- Context Engineering: Building AI Apps That Don't Fall Over at Scale, 2026-09-17.
- Rate Limiting: Every Algorithm, and the Race Condition in the Obvious One, 2026-09-20. Part 1 of the System Design Deep Dives series.
- Building a News Feed: Fan-Out on Write, on Read, and Why You End Up Doing Both, 2026-09-24. Part 2 of the System Design Deep Dives series.
- A Payments Ledger: Why It's Append-Only, and What Idempotency Keys Actually Protect, 2026-09-28. Part 3 of the System Design Deep Dives series.
- Caching in Front of a Database: Invalidation Is the Easy Half, 2026-10-01. Part 4 of the System Design Deep Dives series.
- Queues and Logs: "Exactly Once" Is a Property of Your Handler, Not Your Broker, 2026-10-05. Part 5 of the System Design Deep Dives series.
- Sharding a Database: The Key You Pick Is the One Decision You Cannot Undo Cheaply, 2026-10-08. Part 6 of the System Design Deep Dives series.
- Typeahead: The Only Feature Whose Deadline Is Set by the User's Hands, 2026-10-12. Part 7 of the System Design Deep Dives series.
- Building Chat: "Sent" Is Four Different Facts and the Tick Only Shows One, 2026-10-15. Part 8 of the System Design Deep Dives series.
- Video Streaming: You Are Not Serving a File, You Are Serving Six Thousand of Them, 2026-10-19. Part 9 of the System Design Deep Dives series.
- Matching Riders to Drivers: The Index Is Easy, the Write Rate Is Not, 2026-10-22. Part 10 of the System Design Deep Dives series.
- Notifications: Every Message You Send Spends a Budget You Cannot Refill, 2026-10-26. Part 11 of the System Design Deep Dives series.
- Distributed Locks: The Lock Is Advice, the Fencing Token Is Enforcement, 2026-10-29. Part 12 of the System Design Deep Dives series.
- Selling the Last Ticket: Reservations, Oversell, and the Queue at the Door, 2026-11-02. Part 13 of the System Design Deep Dives series.
- Object Storage: Eleven Nines Is Arithmetic, and the Bucket Is Not a Filesystem, 2026-11-05. Part 14 of the System Design Deep Dives series.
- Observability: Cardinality Is the Bill, and Sampling Decides What You Can Debug, 2026-11-09. Part 15 of the System Design Deep Dives series.

## Pages

- [Services](https://codebrewerz.com/#services) - the seven services CodeBrewerz delivers, plus the engineering blog.
- [Products](https://codebrewerz.com/#products) - LogiHaul, unMail, Hivemind, Snugl, with status and stack.
- [Automations](https://codebrewerz.com/automations) - six free automation templates for n8n, Kestra and Apache Airflow.
- [Blog](https://codebrewerz.com/blog) - long-form engineering writing on the systems underneath a modern product.
- [About](https://codebrewerz.com/about) - who runs CodeBrewerz, how an engagement runs, and the standards the work is measured against.
- [FAQ](https://codebrewerz.com/#faq) - answers on the engagement model, timelines and quotes.
- [Contact](https://codebrewerz.com/contact) - scoping-call request form and business details.