re:MAK3 Ventures invests compute and engineering time, not cash — founders co-build with our members for a fixed term, and we take a stake in what gets made. Talent over capital, the whole way down.
They need a working system, a few senior engineers, and GPUs to run a training loop — and cash buys those things slowly and badly. We provide them directly, in kind.
When the project ends, the hardware is wiped and reallocated — to the next venture, or to an Initiative project, so nothing is sunk. The engineers walk away saturated with new context, and the founder walks away with a system that actually works.
That's what infrastructure-backed venture capital means in practice: the infrastructure renews, the relationship stays.
GPU and CPU capacity drawn from the foundry's pool — no metered bill, no procurement loop.
Two to four members embedded with the founders for the full duration of the build.
Production-grade DevOps, observability, deploy and rollback — ready on day one, not negotiated later.
Access to the wider foundry network — design, legal, hiring panels, and the rest of the bench.
A snapshot of the active book. We keep it small on purpose — embedded work doesn't scale, and the loop only renews if we finish what we start.
A simulation platform for cement chemistry. We provided the GPU farm and three engineers for nine months.
Sub-surface mapping for tunnelling crews. Co-built the inference pipeline and shipped the first deployable beta.
Vision systems for warehouse pickers. Re-architected their training loop; cut iteration time by 8×.
A grid-balancing market for distributed batteries. We designed the matching engine and the audit trail.
“Capital follows infrastructure, and we hold the infrastructure — which means we can back the founders we believe in, not just the ones who can already afford the runway.”Operating doctrine, §6
Two pages, plain prose. We read every one.