The questions operators
actually ask.
If your question is not here, email us. A person who works on the product will answer.
Honest answers,
plainly.
If your question is not here, email us. A person who works on the product will answer.
We are live in Texas, Arizona, Florida, Utah, Louisiana, West Virginia, Iowa, Arkansas, and Missouri, plus a baseline configuration for any state running through ClassWallet. Each new state ships with its vendor registration steps, quarterly report shape, and attendance rule pre-loaded. Tell us your state and we can confirm where it sits in the queue.
No. We work alongside them. Your ESA funds disburse through your state's platform. CohortLedger generates the quarterly invoices, tracks received, pending, partial, and out-of-pocket, and keeps dated records. We make sure the money you are owed comes in on time and documented. We do not move the money ourselves.
No. Your school, your brand, your tuition, your families. CohortLedger is software you use, not a network you join. No revenue share, no required programming, no ranking.
No. We are not a payment processor and we take no cut. ESA funds flow through your state's platform. We invoice, track, and document so nothing slips and you can hand a state reviewer a clean record.
Those tools were built for tuition. They answer one question well: did the family pay what they owe. ESA money does not work that way. It arrives from Odyssey or ClassWallet in uneven tranches, sometimes short, sometimes with a fee taken out, often without a clear invoice reference, while each family sits partly state-funded and partly out of pocket. CohortLedger matches every deposit to the right family and invoice, flags the compliance step that has to clear before the next disbursement releases, and produces the per-student summary a state reviewer asks for, which is not the same as a bookkeeping report. We sit alongside your accounting or tuition software, not on top of it. You keep QuickBooks or FACTS for general tuition, and we own the ESA money flow and the per-state compliance it depends on.
We are built for independent microschools, learning pods, and homeschool co-ops, roughly 5 to 100 students operating under homeschool or private-school rules. We are not built for large district K-12 or licensed daycare and pre-K, which run on different systems and regulations.
We act as a service provider on behalf of the school. Data is encrypted in transit and at rest, US-hosted. We follow COPPA-aware practices, do not display advertising to children, do not sell data, and do not use student records for AI model training. Full details in the Privacy Policy and the DPA.
Yes. Incorporated in the US, terms and privacy policy published, DPA on request. Email through the Contact page and a person answers.
Yes, on request. We provide a standard Data Processing Addendum and are happy to review state-specific addenda for jurisdictions with stricter student data privacy laws (California, Colorado, Connecticut, Utah, Texas, Virginia, plus state-specific student data laws where applicable).