Where human and AI meet.

Nodo is a software studio built on one idea: a person and an AI working as one node make things neither could alone. Web apps, mobile apps, integrations and AI products, for businesses that want more than a vendor.

Start a project See the work

A person. An AI. One node.

Every project here is built by a person and an AI working on the same file, from the first sketch to the last deploy. That is how a studio this small ships web apps, mobile apps, integrations and AI products at a size you would expect from a much bigger one.

Read the six in full
N-01

Web Apps

A web app is software people use, not a page they read: a dashboard, a portal, an internal tool, a product with logins and data. We build them in React and TypeScript, on Astro where content and pages mix with the app, on Vite where they don't. The AI drafts components, wires the API calls, and writes the first pass of a data table from a spec. A person decides the information architecture, checks every edge case a demo skips, and rewrites anything that reads like a machine wrote it. What ships is fast, typed, and accessible, and someone on our side can explain every line of it.4 deliverables
N-02

Mobile Apps

Most small teams don't need two native apps, they need one good one that runs on both phones. We build in React Native and Expo, with Supabase or our own Node.js backend behind it. The AI generates the boilerplate for a new screen and a first draft of the navigation, then a person handles the parts that decide whether the app feels right: gesture timing, offline states, what happens when the network drops mid checkout. We ship through Expo's build and update pipeline, so a fix goes out without waiting on an app store review.4 deliverables
N-03

AI Products

This is the newest service on the list, and it grows the fastest. We build the features that use a model to do real work inside your product: a support assistant that reads your documentation, a summarizer that turns a stack of notes into one page, an agent that files the ticket instead of just drafting it. A person designs what the model is allowed to decide and writes the guardrails. The model handles the parts that don't scale by hand, like reading every document or answering the hundredth version of the same question. We use Claude and OpenAI's APIs, and we test for the failures a demo never shows you.4 deliverablesOpen now
N-04

Integrations

Most of a business's software problems are two systems that don't talk: the CRM that doesn't know about the calendar, the spreadsheet that should have been a form. We connect what you already run, on Node.js, so data moves without someone re-typing it into a second tool. The AI drafts the first version of a sync job and reads a vendor's API docs faster than a person can. A person decides what happens when the sync fails at 2am, and builds the retry logic and the alert that actually wakes someone up. The result is fewer tabs open and fewer numbers that disagree.4 deliverables
N-05

Backends

Every app needs something underneath it holding the data and the rules straight: an API, a database, an auth system that doesn't leak. We build that in Node.js and TypeScript, on Postgres through Supabase or on MongoDB when the data is less structured. The AI writes the first migration and the boilerplate for a new endpoint. A person reviews the data model, decides what needs a transaction and what needs an index, and writes the access rules that keep one customer's data out of another's. Boring is the goal here. A backend that never makes the news is doing its job.4 deliverables
N-06

Care

Software isn't done when it ships. Dependencies go out of date, traffic patterns shift, and the edge case nobody saw in testing eventually finds a real user. We keep what we built running: monitoring, patching, and a monthly block of hours for small fixes and adjustments. The AI watches logs for patterns a person would miss in the noise and drafts a fix for the obvious ones. A person decides which fixes are safe to ship without a full review and which need one. You get a short report every month: what changed, what it cost, what's next.4 deliverables

Six junctions · N-01 to N-06

Two inks. One overprint.

Green is the human hand: taste, judgement, craft. Pink is the AI: speed, range, tireless iteration. Where the two land on the same spot a third colour appears. That colour is the work.

Green · the human hand

Pink · the AI

Sketch, prototype, ship, care.

Four marks on one rule. Nothing moves to the next step until the last one is in register.

  1. 01

    Sketch

    A week of questions and rough screens. You see the shape of the thing before anyone writes code.
  2. 02

    Prototype

    A working slice you can click, on real data. We cut whatever nobody touches.
  3. 03

    Ship

    Small releases, each one reversible. Your people get value while the rest is still being built.
  4. 04

    Care

    We stay on it. Updates, monitoring, and a person who answers when something breaks.

The press · four marks

Work off the press.

Projects we built and still answer for. A person set the direction. An AI held the pace. Every cover below is one sheet of the run.

See all work
08 / 08Live

Apsis

Space Tourism / Aerospace
11Pages
End of the runSee all work

What we are writing about.

Recent notesRead the journal
Aug 1, 2026Product

Integrations are the product

The feature nobody demos is usually the one that decides whether the software actually gets used. Why we treat integrations as core work, not plumbing.

Jun 10, 2026Ship in weeks, not quartersProcessReadApr 22, 2026What the human still decidesAIReadMar 4, 2026An AI in the roomAIRead