Business & sales
Eelgrass puts multi-tenant isolation, audit history, lazy schema rollout, forks, and change feeds in the engine so product teams do not rebuild that control plane per app.
This section is for founders, product leaders, compliance stakeholders, and anyone who has to explain why the architecture matters in a room that does not read B-tree review guides.
Read these three pages
| Page | Audience | Takeaway |
|---|---|---|
| The shift-left bet | Everyone | What leaves the business layer, with diagrams |
| Value for the business | Sales / exec / board | Cost, risk, and differentiation in plain language |
| Capability map | Diligent buyers / partners | Concern → engine home → ships today vs roadmap |
One sentence
In Eelgrass the tenant is the unit of isolation, storage, and lifecycle.
How this fits the rest of the docs
Diagrams render as interactive Mermaid. On a phone, tap to expand, then pinch-zoom or use the on-screen controls.
- Consumers: install, language, Studio, operations
- Maintainers: build, architecture, review
- Status: honesty contract (pre-alpha)
Eelgrass is pre-alpha. Lead with Status when a prospect asks "can we ship on this tomorrow?" Lead with Value when they ask "why would we care when it is ready?"