Our Stack

Our engineering stack.
Tools we use. Why we use them.

We are tool-agnostic but opinionated. Every framework, language, and platform below earns its place in the ComCreate stack because it solves a real problem better than the alternatives, not because it is trendy. Each link goes to a deep-dive on how we use it, where we don't, and what we pair it with.

How we choose what makes it in.

Most agencies pick a stack once and force every project into it. We pick per project, based on what the data needs, what the team can maintain after handoff, and what will still be a good choice three years from now. The tools below have been battle-tested across migrations, AI launches, performance rescues, and production builds for companies that need more than a marketing site.

Three principles guide what gets adopted:

Mature ecosystems first. Next.js, SvelteKit, React, TypeScript, Python. Every framework here has a deep talent pool, active maintenance, and a clear long-term trajectory. No clever bets that orphan a client codebase.
Composable infrastructure. Vercel, Sanity, Stripe, Supabase, Cloudflare. Pieces that fit together cleanly and can be swapped without rewriting the application.
Performance as a first-class constraint. The stack is opinionated about Core Web Vitals, bundle size, and runtime behavior. Slow tools do not make the cut.

Below the categories: frameworks for building, infrastructure for running, content tools for editors, and the languages everything ties together with.

Frontend

The framework behind the majority of what we ship. Server rendering, static generation, and hybrid approaches. Chosen per route based on what the data actually needs.

The component model behind everything we build on the web. Whether it ships inside Next.js, SvelteKit, or a standalone SPA. React is our primary UI layer.

Compiled components, zero virtual DOM overhead, and a framework that stays out of the way. We use SvelteKit for animation-heavy and performance-critical projects.

Every project, every file, every function. Full type safety from database schema to UI component. No exceptions.

Zero JavaScript by default. When a site is primarily content and the performance budget is strict, Astro delivers the leanest possible output.

Infrastructure

Every project gets preview environments, automatic CI/CD, and production monitoring from commit one. No DevOps overhead, no excuses.

We use AWS selectively.AI services through Bedrock, file storage on S3, and compute when serverless is not enough. Not everything belongs on the edge.

DNS, CDN, DDoS protection, and edge caching. Every project we ship sits behind Cloudflare as the first line of defense.

API routes, server-side rendering, build tooling, and backend services. One language across the entire stack.

FastAPI services, AI/ML pipelines, voice agents, and data processing. When the work is computation-heavy, Python is where we go.

When the workload needs a long-running process, persistent connections, or a container that stays alive.Railway hosts it.

When a platform needs to handle thousands of concurrent connections, process events in real time, and never go down. Phoenix, OTP, and the BEAM VM.

CMS & E-Commerce

A headless CMS that gives content teams full autonomy. Structured content, real-time collaboration, and an API that fits how we build.

We use the Shopify Storefront API to build custom shopping experiences, not Shopify themes. The commerce engine stays. The frontend is ours.

Tools

Our design-to-code pipeline starts in Figma. Component libraries, design tokens, and developer handoff. All in one tool.

Growth & Operations

CRM, SMS and email nurture, booking calendars, and closed-loop ad attribution. The system that catches a lead the second a form is submitted and works it until it closes.

Dynamic number insertion ties every inbound call back to the campaign, keyword, and landing page that drove it, so phone leads count as conversions instead of guesses.

Our operations-side call platform for PPC. Number pools, routing rules, and conversion data across a whole book of client accounts in one place.

We integrate Yardi through its SOAP API so leads captured on the site land in the property CRM in real time, with the source data intact for attribution.

The EHR and CRM behind addiction treatment and behavioral health. We connect the website and ad funnels to Kipu so inquiries reach intake fast, with attribution intact.

Get started

Let's talk about
your next build.

Talk to an engineer