The FastYoke Blog

Engineering & product notes

How the platform is built, and why. RSS

Type-level multi-tenancy: making "forgot the WHERE tenant_id" impossible

Tenant isolation is too important to leave to code review. Here is how the type system refuses to compile a query that forgets its tenant scope.

FastYoke Engineering · 8 min read · Jul 6, 2026

Architecture
Multi-tenancy
Rust
Security

The seat is dying: SaaS pricing when software gets cheap to build

For twenty years enterprise software meant renting seats in someone else's database-with-business-logic. AI is making that logic cheap to generate — and the pricing model built on it is cracking.

FastYoke Engineering · 10 min read · Jul 4, 2026

Opinion
SaaS
AI
Pricing

Getting internal apps onto employee phones — without the App Store

Regulated enterprises need internal apps on employee devices — but the public App Store is the wrong path. Here's the problem, and why we built FastYoke Substrate.

FastYoke Engineering · 9 min read · Jun 20, 2026

Mobile
Enterprise
Compliance
Substrate

Sovereign git, config as code, and how we built the Vault

If a customer's data and config should truly be theirs, git is the natural substrate. We already put our source and CI on self-hosted Forgejo — the Vault extends that to tenant data.

FastYoke Engineering · 9 min read · Jun 6, 2026

Sovereignty
Git
Audit
Config-as-Code

Why we built our own CI — in Go

We run on self-hosted Forgejo and needed CI we control and can reproduce over a huge Rust build. So we built it — with Dagger and a small Go gateway. Here's why Go, not Rust, for this layer.

FastYoke Engineering · 9 min read · May 23, 2026

Go
CI/CD
Dagger
Sovereignty

Running your code — safely, at native speed: why FastYoke chose WebAssembly

Every FastYoke tenant runs logic we didn't write, on shared infrastructure and hardware we don't control. Here's the sandbox that makes that safe — and fast.

FastYoke Engineering · 10 min read · May 9, 2026

WebAssembly
Multi-tenancy
Security
Sovereignty

FastYoke DB: why we ship two flavors of distributed SQL

Our default is a database file per tenant. For the workloads that outgrow a single VM, FastYoke DB is our roadmap for managed distributed SQL — designed around two engine flavors, with the same app code across both.

FastYoke Engineering · 8 min read · Apr 25, 2026

Databases
Architecture
SQLite
Distributed SQL

Why the FastYoke core is written in Rust

A multi-tenant engine that has to be memory-safe by construction — shipped as a single small binary that runs in the cloud, on-prem, and air-gapped. Here's why the core is Rust.

FastYoke Engineering · 9 min read · Apr 11, 2026

Rust
Architecture
Multi-tenancy