Products, platforms, and the AI inside them.

01 CommitBB Dev, product engineering and DevOps

We build web and mobile products, the platforms that run them, and the AI and data systems that work inside them. We also take on platforms we did not build: DevOps, cloud security, the bill. Then we keep them running, on the same pipeline that built them.

Start a project

a41f9c2mainfeat: the whole site

02 BuildWhat we do

What we build.

Six areas of work, building new or taking on what you already run. Most projects touch two or three of them, and the same engineer sees each one through.

The shape of a system we build and runrequests, jobs, models, stores
  1. Platform, DevOps and security

    Pipelines, clusters, cloud accounts and the observability to run them. We build platforms, and we review the ones you already have: access, secrets, network, logging, cost.

    KubernetesGitHub ActionsAWS, GCP and AzureSecurity reviewIAM and secretsCost control

    Talk to us about platform, devops and security
  2. Web applications

    Product engineering from a blank repository to launch. Modern stacks, sensible choices, and tests that earn their keep.

    Next.jsReactTypeScriptPostgresRealtimeDesign systems

    Talk to us about web applications
  3. Mobile and desktop

    iOS, Android and Mac apps that share a backend with the web. Cross-platform where it is right, native where it matters.

    ExpoReact NativeSwiftUITauriApp Store releaseOffline first

    Talk to us about mobile and desktop
  4. AI and automation

    Agents that read your data, call your tools and finish tasks. Evaluated before they are trusted, observed once they are live.

    AgentsRetrievalVoiceLocal modelsEvaluationsClaude and OpenAI

    Talk to us about ai and automation
  5. Data pipelines

    Extract from dozens of sources, harmonise the schemas, and land it somewhere fast enough to ask real questions of.

    ClickHouseConnectorsOAuth integrationsWarehousingDashboardsScheduling

    Talk to us about data pipelines
  6. Web3 and smart contracts

    EVM contracts and the dApps around them. Mints, staking, marketplaces and the backend that keeps a game economy honest.

    SolidityEVMWallet authMarketplacesStakingToken economies

    Talk to us about web3 and smart contracts

03 TestSelected work

What we have built.

Described by shape rather than name. Seven products we designed, built and put into production, and two platforms we were brought in to secure and run. All still running.

The figures are the real architectures, simplified. Most of the work is under NDA, so ask on a call and we will walk you through the ones nearest yours.

  1. 01 · Consumer✓ passed

    A guided consumer product that hands people one thing at a time

    Product design · Web and mobile apps · Content system · Hosting and support

  2. 02 · B2B SaaS, planning✓ passed

    A collaborative planning canvas with live cursors and an AI copilot

    Realtime sync · Canvas rendering · Auth and billing · LLM tooling

  3. 03 · Martech, data✓ passed

    A marketing data platform that loads dozens of ad sources into one warehouse

    Connector framework · Transform layer · Managed ClickHouse · Customer dashboards

  4. 04 · AI, operations✓ passed

    A self-hosted multi-agent system reachable from Slack, Discord and Telegram

    Agent orchestration · Tool integrations · Memory and retrieval · Self-hosted deployment

  5. 05 · Developer tooling✓ passed

    A preview environment platform that spins up a full stack per pull request

    Platform engineering · Kubernetes · Config format · Cost controls

  6. 06 · Regulated records✓ passed

    A records platform with a tamper-evident audit trail

    Records model · Audit chain · Verification · Companion app

  7. 07 · Gaming, Web3✓ passed

    A game economy with runner and staking dApps on EVM contracts

    Smart contracts · Marketplace dApp · Game backend · Cloud infrastructure

  8. 08 · Cloud security✓ passed

    A security review and hardening of a cloud estate we did not build

    Security review · IAM and secrets · Network hardening · Runbooks

  9. 09 · Platform, DevOps✓ passed

    A production platform taken over from the team that built it

    Pipeline · Monitoring and alerting · Backups and restore drills · Cost control

04 MergeWorking with us

How a project runs.

Five steps. Each one merges into main before the next begins, so there is never a handover at the end.

  1. Brief.

    A call and a short written brief. We say plainly whether we are the right team for it.

  2. Plan.

    Scope, architecture, timeline and price. Yours to keep, whether or not we go ahead.

  3. Build.

    Weekly demos, a staging environment from day one, and a pipeline that deploys every merge.

  4. Launch.

    Monitoring, backups and runbooks in place before the first real user. Documentation you can read.

  5. Run.

    Support on retainer if you want us to keep it running, from the engineer who built it.

05 DeployHow it ships

Deploys this visit 00

Commit. Build. Test. Ship.

Every merge deploys. A staging environment from day one and a pipeline that runs on each pull request: a preview to click, migrations that run themselves, a rollback in one command. The same pipeline stays with the product after launch.

06 ObserveClients

Who we work with.

Six kinds of client, one way of working. If yours is not on the list, the answer is probably still yes.

  1. Startups

    Pre-seed to Series B. A first product, or the rebuild after the prototype hit its limits.

  2. Scale-ups

    An engineering team that needs a platform, a data layer, an AI capability or a security review faster than it can hire.

  3. Agencies

    Design and marketing agencies that need an engineering partner behind their client work.

  4. Enterprise teams

    Innovation and product teams that need something real shipped, or an existing platform reviewed, outside the usual procurement gravity.

  5. Founders with a spec

    A clear idea, a budget, and the need for a team that will tell you what it costs before it starts.

  6. Web3 projects

    Token launches, collectable economies and the dApps that make them usable.

  • Observed in productionNext.jsReactTypeScriptTailwindExpoReact NativeSwiftUITauriNodePostgresClickHouseRedis
  • And the platformKubernetesDockerGitHub ActionsAWSAzureCoolifyTerraformGrafanaClaudeOpenAIvLLMSolidity

07 DeployedGet in touch

✓ deployedeu-west-2p95 142ms0 errors

Let's build it.

Write to contact@bbdev.app with what you need built and kept running. You hear back from the engineer who would do the work, with a plain answer on whether we are the right team for it.