Trust
Security and data practices
BrewLogs is built for brewery production records, so access boundaries, roles, backups, and careful wording around compliance matter.
Workspace access and roles
BrewLogs uses tenant workspaces with owner, admin, member, and viewer roles. Viewer access is read-only, while member and admin roles are used for production data changes according to the apps authorization rules.
Authentication and verification
The app supports authenticated access and email verification gates for workspace access. Google sign-in users are treated through the configured provider flow.
Backups and recovery planning
The repository includes a Firestore backup runbook for scheduled exports to Google Cloud Storage with lifecycle retention. Production teams should verify the actual bucket, retention policy, and alerting setup for their deployed environment.
What BrewLogs does not claim
BrewLogs helps organize production records. It does not guarantee regulatory compliance, certify safety, replace laboratory testing, or make production decisions for a brewery.
Related kombucha production pages
Frequently asked questions
Does BrewLogs support read-only users?
Yes. The product model includes a VIEWER role intended for read-only access.
Are backups automatic in every deployment?
The repository includes backup infrastructure and documentation. Each production deployment should verify that scheduled backups, retention, and alerting are configured for its environment.
Does BrewLogs guarantee regulatory compliance?
No. BrewLogs helps breweries organize production records and review fermentation data. Each brewery remains responsible for testing, compliance, labeling, and production decisions.
Start building cleaner kombucha production records
BrewLogs helps breweries track batches, recipes, pH, gravity, flavor production, and fermentation trends in one organized system.