About
Who builds Trazo, and how
Trazo is built by Oscar Munoz, a software engineer building the product end-to-end and working directly with organic specialty-crop growers and certifiers in California and Washington. No sales team between you and the person who writes the code: the questions farmers ask become the next release.
One thesis, applied everywhere
A farmer's record should be written once and work twice — as the compliance record a certifier reviews, and as the story a buyer can check. Every feature is judged against that: if it doesn't make the record more complete or more usable, it doesn't ship.
Built on public standards, not private ones
The guided plan follows the USDA-supported Common OSP structure. Emission calculations use EPA/USDA-published factors. Record checks cite the actual regulation (7 CFR Part 205) line by line. The full methodology is published under CC BY 4.0 — including its limitations.
English and Spanish, as equals
The people doing the field work often speak Spanish; the reviewer reading the file usually reads English. Trazo treats both as first-class: log in either language, and the record serves both readers.
What we won't claim
Trazo doesn't certify anything — your certifier does. Records in Trazo are farmer-reported; readiness checks are preparation aids, never findings. You will not find invented statistics, purchased badges, or a "verified" label we granted ourselves anywhere in the product. If a claim can't survive an inspector reading it, it doesn't belong on a farm's page — or on ours.
Talk directly to the builder
Questions, doubts, a certifier form we should support — write and the person who builds Trazo answers. Async, no sales call.