We build the software
that runs things.

By Accident Solutions is the engineering half of By Accident. The agency side markets businesses; we build the systems those businesses run on. Same people, same DNA, different weapon.

Real software,
on a real URL.

Default mode: working software on a real URL early, evolving in plain sight. When the right call is a Figma click-through first — for stakeholder validation, an investor demo, an alignment call before commit — we'll ship that too. The deliverable matches the engagement, not the other way around.

AI is part of how we work — code review, test drafts, log triage, and a real share of generation when it earns its place. The mix shifts with the work: internal tools lean on AI more, money-moving paths get more human review. Either way, every line in production is one we can read and defend.

step 0101 of 3

Working URL, not slides

You see the build running on a real URL as soon as there's something to look at — and on every meaningful change after. No "pending review" screens, no interactive Figmas passed off as builds.

─►
step 0202 of 3

Own Your Stack

You get the repo, the keys, the docs, the deploy pipeline. We leave you with a system, not a dependency.

─►
step 0303 of 3

AI as Infrastructure

We use AI to move faster — code review, test generation, log analysis. We do not use AI to hide who wrote the code.

Boring tech, picked on purpose.

We pitch the stack we already know in production. Each tool earns its slot — no resume-driven dependencies.

// languages
typescripteverything that ships
javascriptlegacy & vanilla work
phpwordpress & laravel apps
pythonai pipelines, scripts
sqlpostgres, mysql, plain
// frameworks
nuxt / vuefrontends, marketing
node / honoapis, services
expressnode apis, integrations
laravelphp apps, business systems
tailwindstyling, design tokens
// cms / commerce
wordpresscontent sites where cms wins
woocommercecommerce on a wp foundation
shopifystorefronts, fast time-to-live
// data
postgresdefault for almost everything
mysql / mariadbwordpress, woocommerce, legacy
redisqueues, caches
sqlitesmall, embedded use
// ai
openai apigpt-4 family for general
anthropicclaude for long-context
pgvectorrag, embeddings, search
// infra
dockerevery app, every env
cloudflaredns, cdn, workers
fly.io / vercelhosting, by fit
// ops
sentryerrors, perf traces
github actionsci/cd, every repo
uptime checkshttp + tcp probes

We eat our own cooking.

This site is one of the stacks we ship — Nuxt + TypeScript fit a fast, owned marketing site. Other projects pick different tools (WordPress and WooCommerce for content and commerce, Shopify for storefronts, custom Postgres apps for software). The handover hygiene stays the same.

this.site
{
"stack":"Nuxt 4 · Vue 3.5 · TypeScript · Tailwind",
"rendering":"SSR + hydration · @nuxt/image for assets",
"hosting":"Docker (Node 24-alpine) · multi-stage build",
"scaling":"Docker Swarm · horizontal scaling · load balancing · zero-downtime deploys",
"analytics":"consent-first — no cookies set unless you accept",
"forms":"Zod validation · honeypot · server-side rate limit",
"a11y":"prefers-reduced-motion respected · keyboard nav · semantic landmarks",
"build":"v1.0.2 · local · deployed 2026-05-07"
}

Let's build
something real.

No pitch decks. No committees. A focused conversation about what you need built, who uses it, and what it has to do.