Dual Core
Two senior engineers, one team. We build your product end to end, and you talk to the people who write the code.
- Two people
Both senior. Nobody else.
No juniors and no account managers. The people on the call are the people who write the code.
- Two weeks
Working software, early.
You see a real, running version within the first two weeks. Not slides, not a design file.
- One team
Interface to infrastructure.
The screens, the data and the deploys come from the same two engineers, so nothing is lost in a handoff.
We build the whole stack. No handoffs.
A product is one system, not a frontend and a backend stapled together. We build it as one — the same two engineers own every layer, so nothing is lost at a border crossing between design, interface, and the systems underneath.
The interface
WHAT USERS SEE AND TOUCH
- Product UIThe screens people actually work in, day to day.
- Design systemsComponents that stay consistent as the product grows.
- Interaction & motionFlows that feel considered, not clunky.
- AccessibilityUsable with a keyboard, a screen reader, any device.
- Front-end performanceFast to load, smooth under real-world use.
The systems
WHAT HOLDS IT UP
- Data modelsSchemas that survive the next feature, not just this one.
- Payments & moneyBilling, subscriptions, and ledgers that reconcile.
- Auth & multi-tenancyAccounts, roles, and hard tenant isolation.
- APIsTyped contracts other services can actually rely on.
- Infra & deploysCI/CD, monitoring, and the pipeline that ships it all.
Two senior engineers. One team, one codebase, one deploy pipeline.
The people who design the interface are the people who build the systems beneath it — so there is no translation loss where the two meet.
Three shapes of work.
Most projects fit one of these. Each has a fixed length and ends with something you can open and use. We agree the scope in writing before any work starts.
- Sprint2 weeks
One clear problem, solved.
A feature, a prototype, or a rescue job on something that is stuck. Small enough to start next week.
You end withWorking code in your repo - Build6–10 weeks
A first version, from zero.
We take an idea to a product real users can sign up for: the interface, the data, the payments and the deploys.
You end withA live product you own - OngoingA few days a month
We stay after launch.
Fixes, new features and steady care, from the two people who already know every corner of the codebase.
You end withThe same two engineers
Things we built because we wanted them.
We are a new studio, so there is no wall of client logos here. This is our own work instead: a book, and the open source tools we use every day. All of it is public, so you can judge the code for yourself.
It Depends: TypeScript Principles, Debated
Eliraz wrote the book on TypeScript trade-offs. A team of fifteen developers argue the hard questions, and every argument is tested against working code.
pr-watch
A live pull request pane for Claude Code. CI status, reviews and merge conflicts for every PR a session touches, without opening the browser.
M-x Machina
An Emacs package for running several coding agents side by side. Each agent gets a name, its own Git worktree and a conversation you can resume.
The stack we actually ship on.
Two cores, one system. The interface core is what a customer touches; the systems core is what keeps it correct when data and money are on the line. This is the tooling we reach for by default — chosen for boring reliability over novelty.
- Next.js 16App Router · RSC
- React 19Server Components · Actions
- TypeScriptStrict, end to end
- Tailwind CSSUtility styling
- Design systemsTokens · components · a11y
- PlaywrightEnd-to-end tests
- RTL & i18nnext-intl · bidi
- Core Web VitalsPerformance budgets
- Neon PostgresServerless SQL
- Drizzle ORMTyped schema · migrations
- Stripe ConnectMarketplace payments
- Vercel BlobObject storage
- Vercel AI GatewayModel routing
- Cron & Fluid ComputeScheduled · long-running
- WebhooksEvent-driven sync
- Rate limitingAbuse protection
- Multi-tenant authPer-tenant isolation
Tell us what you're building.
Two engineers, direct. No account managers, no discovery-call funnel. Send the shape of the problem — the product, the stack, the deadline, where it hurts — and we'll tell you plainly whether we're the right pair for it.
Within three working days we send back a one-page plan: what we would build, in what order, and how long it takes. It is yours to keep, whether you hire us or not.
Want to talk it through? Ask for a call and we'll send a few times that work.
meet@dualcore.techOpen in GmailOne inbox, both of us read it. Best for anything with detail — a brief, a repo, a spec.
team@dualcore.techOpen in Gmail- BARYCENTER
- Tel Aviv
- DEPLOYS TO
- fra1