ODIGO_

Our stack

The tools we use to ship ops systems

Same building blocks we use at Odigo Works for mid-size enterprises. Signup links, what each one is for, and why it shows up in our builds.

We keep the stack boring on purpose. Fewer vendors, clearer ownership, faster fixed-scope delivery. This page is a living catalogue. Start here if you are using the free Automation Quickstart, or if you want the same tools we run on client work.

Get the free Automation Quickstart →

Your coding agent

An AI coding agent that works inside a real project folder, not just a chat window.

In our builds: Scaffolding apps, iterating on forms and workflows, writing the boring glue code so humans stay on scope and review.

Vercel

Hosting and previews for modern web apps (especially Next.js).

In our builds: Public URLs, preview deploys, env vars, and shipping internal tools without babysitting servers.

Supabase

Hosted Postgres with auth, storage, and simple APIs.

In our builds: Jobs, leads, statuses, documents, and the system of record behind field-to-office workflows.

Next.js

The React framework we usually ship on.

In our builds: Intake forms, office dashboards, and fast internal apps that deploy cleanly to Vercel.

PostgreSQL

The database under most serious business software.

In our builds: Durable records you can query, back up, and own. Usually via Supabase in our builds.

Stripe

Payments infrastructure.

In our builds: Checkout, invoicing hooks, and paid products when a client needs money movement in the product.

Resend

Transactional email for product notifications.

In our builds: “New job submitted” pings, magic links, and operational alerts without fighting a marketing ESP.

GitHub

Source control and the home of the repo.

In our builds: Code, reviews, and the connection into Vercel deploys.

How we pick tools

Building this yourself? Start with the free pack.

Get the free Automation Quickstart

Odigo Works is principal-led by Mason DuPree in Greenville, SC. Back to Odigo Works