Tech stack

Five layers under every build

A tech stack is the set of tools a piece of software is built with and runs on. Ours is arranged in five layers, assembled in the same order on each build: build, security, infrastructure, integration and implementation. The tools on a layer change from job to job. The order does not.

Each card is a tool in the Paddock20 stack. Once a day we read the numbers each vendor reports for Paddock20, and a card shows its number with the time it was read.

Want to see where those tools sit? See the products on the Repo Atlas.

35 toolsMeasured 4 read from the vendor, dated on the cardIn use 31 in the stack, no number shownLast read Oct 26, 6:07 AM CT

Build stack

What the software is designed and written with

Where a written scope becomes screens and code, with each change kept in version control.

In use

Claude

Anthropic

Scopes the work, writes code and reviews it.

In use

ChatGPT

OpenAI

Second opinions and first drafts.

In use

Gemini

Google

Long research runs and a third opinion.

In use

v0

Vercel

Turns a written brief into working screens.

In use

Figma

Design

Wireframes and screen layouts before any code.

In use

Replit

Experiments

Quick experiments, tested in the browser before they get a repository.

In use

GitHub

Source code

Source code and the history of each change.

In use

Chrome and iOS

Testing

Where screens get checked, on a desktop and on a phone.

Security layer

What gets set up before launch

Domains, sign-in, credentials and the network edge are configured before anyone outside can reach the system.

In use

Cloudflare

Network edge

DNS, caching and firewall rules in front of the site. Paddock20 resells Cloudflare.

In use

Google Cloud

Credentials

Google sign-in, service accounts and API keys.

In use

Better Auth

Sign-in

Accounts, passwords and sessions.

In use

Namecheap

Domains

Domain registration.

In use

Domain Lock

Paddock20 rule

A visitor who opens a raw .vercel.app preview address is sent to the real domain.

Infrastructure

What runs the system in production

Hosting, the database and the scheduled jobs that keep the data current.

Measured

Vercel and Next.js

Hosting

Hosting, deploys and the scheduled jobs for this site.

Production deploys

162

This site, last 30 days · Vercel · Oct 26, 6:07 AM CT

In use

Neon

Database

Postgres for leads, bookings, call logs and check-ins.

In use

Supabase

Database

Sign-in, file storage and Postgres when a build calls for it.

This site, counted from its code on Oct 23, 2026:

165page routes
118API routes
11scheduled jobs

Integration layer

Where a build meets the systems a business already runs

Payments, search data, spreadsheets and the software a business already uses.

In use

Stripe

Payments

Checkout for the Fit Call and the course library.

Measured

Google Search Console

Search data

Search impressions and clicks for this site, reported by Google.

Search impressions

486

Last 28 days · Google Search Console · Oct 26, 6:07 AM CT

In use

DataForSEO

Search research

Search volume, rankings and backlink data for research and reports.

In use

Google Sheets

Spreadsheets

Read from and written to when a business already keeps its numbers there.

In use

Microsoft 365

Office software

Mail, files and calendars for clients who run on Microsoft.

In use

Composio

Connectors

Ready-made connectors between apps.

Client system

Ran in production

Lot Assistant

Inventory data from an exotic and luxury automotive retailer and wholesaler fed the lot software built for it.

Read the Lot Assistant case

Your business

Your systems

The software your business already runs. The Fit Call is where we check what it can connect to.

See what the Fit Call includes

Implementation layer

Tools added when the problem calls for them

Email, phone, scheduling and automation. A build gets only the ones its problem needs.

Measured

Resend

Email

The confirmations, receipts and alerts this site sends.

Emails delivered

967

Last 30 days · Resend · Oct 26, 6:07 AM CT

Measured

Retell AI and ElevenLabs

Voice

The voice agents that answer calls, and the voices they speak with.

Inbound calls handled

375

Across our voice agents · Retell · Oct 26, 6:07 AM CT

In use

Cal.com

Scheduling

Booking for the free Warm-Up Lap and event calls.

In use

n8n

Workflows

Workflows that run on a schedule or a trigger, from one app to the next.

In use

Google Maps

Location

Places, routes and distances when a build needs a map.

Running the studio

What runs Paddock20 itself

Not part of a client build. These run the studio's own office, mail, design work, video and listing.

In use

Google Workspace

Studio office

Docs, calendars and shared drives.

In use

Gmail

Studio mail

The studio inbox.

In use

Google One

Backups

Backups of studio files.

In use

Canva

Design

Decks, social graphics and print.

In use

Higgsfield AI

Images and video

Images and video for this site, including RAIL and Amy.

In use

YouTube

Video

Video hosting.

In use

Google Business Profile

Local listing

The studio listing in Google Search and Maps.

In use

Google Analytics

Site traffic

Visits to this site and where they came from.

The Next Step

Tell us the part of your week that should not exist anymore.

Describe the problem as it actually is. The 2Box Method cuts it in half: the data and the experience, and the workflow that connects them. The 3D system scopes it, prices it in writing, and ships it. You get a straight answer on the first call: a number, or an honest no.

Book a Fit Call · $249
Scope it with RAIL
Paddock20Digest. Develop. Deliver.
Paddock20 · Nashville, TN · Bay #20