Formula Keeper

Docs API Sign in

Getting started

How teams establish the workspace and sequence the first records.

Operations

How materials, formulas, vendors, and batches fit together as one working system.

Governance

Custom roles, audit history, support administration, and launch guardrails.

Getting Started

How teams enter the workspace, create a tenant, and establish the first operational records.

Create or join a workspace through Formula Keeper authentication.

Establish workspace naming, record-ID policy, and baseline roles before operators begin entering records.

Start with raw materials, then formulas, then batches and vendor sourcing so downstream views have clean lineage.

Operations Workflows

The working surface for day-to-day formulation, inventory, vendor, and production activity.

Raw material records support taxonomy, revision history, sourcing, pricing, and regulatory review flags.

Formula detail supports composition, costing, versioning, and downstream usage context.

Batch detail acts as the operator workbench for run state, QC, pricing, genealogy, and traceability.

Governance & Access

How Formula Keeper controls permissions, audit history, and internal support posture.

Workspace access is role-aware and can be narrowed further with custom permission bundles.

Record revisions and audit history remain available for investigation and export.

Internal support access is read-only, time-boxed, and logged through support audit events.

Launch Posture

What is production-ready now, and what remains intentionally deferred after the internal launch.

Core operational workflows are live for materials, formulas, batches, vendors, RBAC, audit, and support.

Billing and Stripe-driven entitlements remain out of current launch scope.

The public API is still deferred until a real versioned surface exists.

Developer surface

API docs are live as a real navigation surface.

The versioned `v1` preview API now exists, and the docs shell gives teams one place to understand the route baseline, current session-or-key auth posture, and the remaining compatibility work without inventing a larger surface than has actually shipped.

Open API docs