Belay Studio

Belay Studio — Engineering studio

We build platforms. And the AI agents that run them.

AI systems, infrastructure and web products, from one LLM integration to a team of agents that develops, tests and deploys your platform. We build it, and we stay to run it.

In production BaseadosTVvest101Kandrax RolWorld of KandraxMister DokuOsler·MD

  • Claude
  • Anthropic
  • xAI
  • Grok
  • Gemini
  • OpenRouter
  • LangGraph
  • LangChain
  • Langfuse
  • Qdrant
  • Kubernetes
  • Docker
  • Terraform
  • Ansible
  • AWS
  • Google Cloud
  • Cloudflare
  • GitLab
  • Grafana
  • Python
  • FastAPI
  • Node.js
  • TypeScript
  • React
  • Flutter
  • PostgreSQL
  • Redis
  • Stripe

What we do

Three things, done by the same people

Most teams split AI, infrastructure and product work. We do all three, so the model, the servers and the interface fit together.

AI systems

From one LLM call to a team of agents that runs a platform.

  • LLM integration: Claude, GPT, Gemini, Grok, open models, OpenRouter
  • Chatbots and support bots that answer from your own data
  • Agent networks that operate a platform or a media channel
  • Private AI on your own hardware
How we do it : AI systems

Infrastructure

Platforms that stay up, in the cloud or in your own racks.

  • Kubernetes on AWS, Google Cloud or on premise
  • Infrastructure as code with Terraform and Ansible
  • CI/CD with a staging step and a production approval
  • Monitoring, alerts and backups
How we do it : Infrastructure

Web & mobile

Full-stack products, from the database to the app store.

  • Web apps with React and TypeScript
  • APIs with Node.js and Python
  • iOS and Android apps with Flutter
  • Payments, live video and real-time features
How we do it : Web & mobile

AI agent networks

A team of agents ships the change. You approve it.

We build networks of AI agents that work as an engineering team. Each agent has one role and its own rules. The agents take tasks from your tracker, write and test the code, release it and report. A person decides at each gate.

How we build agent networks

How one change goes from the tracker to production

  1. Manager agent

    Picks the next task

    It reads the issue tracker and proposes the most important task that an agent can do.

  2. You

    Approve the task

    One message. For a complex task you also approve the plan before any code exists.

  3. Developer agent

    Plans, codes and tests

    Simple tasks go to a fast agent. Complex tasks go to a planning agent on a frontier model.

  4. Release agent

    Tags and deploys to staging

    One agent owns the release candidates. It checks the pipeline and reports each failure.

  5. QA agent

    Tests on staging

    It tests the change as a real user, with screenshots, and sends problems back.

  6. You

    Say “deploy”

    Production gets the same build that passed staging. Then QA checks production and you get the release notes.

An agent works A person decides

The roles in a network

  • Head manager Owns the rules and the production release.
  • Team managers Propose tasks and relay your approvals.
  • Planning developers Complex, multi-repository tasks.
  • Fast developers Small, single-repository tasks.
  • Release agent The only one that tags a release.
  • QA agent Tests staging and production.
  • Mobile agent Builds, signs and uploads the app.
  • Analyst Read-only reports on code and changes.

In production today: one network develops and releases a software platform, and one network operates a full media channel. See Kandrax Rol

Our work

Projects

Products in production and confidential systems on premise. Each one has its own page.

Technology

The tools, and how we use them

A tool is only a name until someone uses it well. For each one, the technology page says what we do with it, and it links to the project that proves it.

See the full technology page

About us

Two founders. Both engineers.

Engineers with complementary skill sets and one shared belief: technology must serve a purpose beyond itself.

Portrait of Javier Moure

Javier Moure

CTO Infrastructure & engineering leadership

Engineer with deep experience in infrastructure, automation and AI tools. He leads engineering teams, designs cloud, hybrid and on-premise systems, and keeps a strong product mindset.

  • Infrastructure
  • Cloud & hybrid
  • AI tools
  • Automation
  • Platform engineering
  • CI/CD
Portrait of Federico Pérez

Federico Pérez

CAIO AI & full-stack engineering

Engineer driven by curiosity across hardware, frontend and Gen AI. He turns technical complexity into clear solutions, and sees technology as a means to build something meaningful.

  • Gen AI
  • AI agents
  • Full-stack
  • Software architecture
  • Frontend
  • Backend

Questions

Before you write to us

Short answers to what clients ask first.

What does Belay Studio do?

We are an engineering studio. We build AI systems, infrastructure and web and mobile products, and we run them in production. Typical work: an LLM integration, a chatbot on your own documents, a network of AI agents, a Kubernetes platform, or a full product from the database to the app store.

Can you add AI to a product that already exists?

Yes. We connect your product to the model that fits the job, through a direct API (Anthropic, OpenAI, Google, xAI) or through OpenRouter. We add retrieval on your own data, guardrails, cost limits and traces, so you can see what each answer cost and why the model gave it.

What is an AI agent network?

It is a team of AI agents with different roles. In a software team, the agents take tasks from your tracker, write and test the code, deploy to staging and report, and a person approves each task and each production deploy. In a media team, the agents edit the recordings, publish them and maintain the web site.

Can the AI run on our own servers?

Yes. We have built on-premise AI systems, for example a document chatbot that anonymizes sensitive data and a live camera tracking system. When data cannot leave your building, we use open models and local embeddings on your hardware.

Do you work on an existing codebase?

Yes. We work on large, multi-repository codebases every day, with Claude Code and with our own agent networks. We write the requirements first, we approve a plan before the code, and tests decide if a change is ready.

How do we start?

Send us an email and tell us what you want to build or fix. An engineer reads it and answers.

Let's work together

Tell us what you want to build or fix. An engineer answers.

Contact us