Ee

ee

Grida is open source. Some features only exist because Grida is also a hosted commercial product — org-level entitlement, custom domains, billing. Those features are EE (enterprise edition): they ship in the same monorepo as the OSS core, but a self-hoster running the codebase without paid infrastructure should be able to identify and strip them.

This skill is the anchor for that boundary. No GRIDA-EE marker exists in the repo today; this skill establishes the convention.

What counts as EE

The test: would this feature still make sense in a single-user, no-billing self-hosted instance? If no, it is EE.

Three surfaces today:

• Org / entitlement — the commercial layer on top of multi-tenant routing. Paid plans, member seats, the entitlement check that gates paid features. The tenant routing substrate itself ((tenant) route group, RLS, hostname resolution) is OSS infrastructure — only the commercial layer on top of it is EE.
• Custom domains (BYOD) — user-owned apex + subdomain mapping on Vercel. See multi-tenant-custom-domain-vercel.
• Billing — subscriptions, AI credit, the entitlement gate primitive. See the ee-billing skill (planned) for the workflow.

The GRIDA-EE marker

Like GRIDA-SEC, the boundary is grep-able. Tag every file that exists only for EE, with the surface as the sub-label:

// GRIDA-EE: entitlement — paid-plan gate
// GRIDA-EE: byod — apex domain verification
// GRIDA-EE: billing — see ee-billing

Sub-labels are surface names (entitlement / byod / billing), not ids — there is no central registry like SECURITY.md. The grep is the index:

grep -rn 'GRIDA-EE' editor crates packages

Tag the file header when the entire file is EE; tag inline when only a branch is EE.

Known limitation. The marker captures files that exist only for EE. Shared utilities that EE imports but OSS also uses are not tagged — strip-time discovery has to come from an import audit, not grep. Don't tag OSS modules with EE callers; tag inline at the EE branch instead.

Physical placement

Co-locate by surface so the grep doesn't have to do all the work.

• Next.js routes — group under (ee) only when a cluster of EE-only routes shares chrome/auth distinct from OSS readers (per naming, route groups encode the reader on the other side of the screen). For a single EE route inside an OSS reader's surface, tag inline rather than fragmenting the existing group. Tenant content rendering stays in (tenant) — that is the OSS routing substrate, not EE.
• Packages and crates — use the existing *-hosted suffix when the whole package is EE-only. grida_hosted already lives in the DB schemas as the parallel namespace, and *-hosted is in naming's established suffix list. Don't mint a parallel *-ee suffix. Mixed packages stay unsuffixed and tag the EE branches inside.
• Database — namespaced schema. Existing examples: grida_billing, grida_hosted. Don't bleed EE columns into OSS-relevant tables. Schema-design rules live in the database skill / supabase/AGENTS.md; consult those.

When in doubt, default to the EE-named location. The cost of moving later is the cost of every import.