Enrollment signed where learning lives: in your platform.
Embedded signing for enrollment, admissions, and student-services platforms. Permission slips, financial agreements, and staff paperwork signed by parents and students on any device.
Domain or work email: either way you get a branded account. No credit card, no sales call.
Just need an API key? Create a plain account
The signing workflows your platform carries
Enrollment and admissions
Applications and enrollment agreements pre-filled from your student records, signed and filed without paper.
Permissions and consents
Field trips, media releases, and policy acknowledgments routed to parents and guardians, tracked to completion.
Financial agreements
Tuition agreements, payment plans, and aid documents with the audit trail the business office expects.
Staff and faculty paperwork
Offers, renewals, and handbook acknowledgments signed inside the system your schools already use.
Multi-tenant white-label, built in
Each school, district, or program on your platform gets its own experience.
Every tenant, their own brand
White-label works at the multi-tenant level. Each of your customers gets a branded experience: their logo, their colors, their domain, their emails. Not yours, and never ours.
Own the SKU
Package, price, and sell signing as part of your product. Usage-based platform pricing leaves the margin, and the customer relationship, with you.
Aligned by design
We sell through you, not around you. Your success selling downstream is the business model, so partner support is the product, not a program.
Common questions
Can parents sign permission forms on their phones?
Yes. Parents and guardians sign from an emailed link on any device, with no account to create.
Can a form route to multiple guardians?
Yes. Parallel and sequential routing handles multiple guardians, staff approvers, and carbon copies in any order.
Can each school or district on our platform have its own branding?
Yes. White-label operates at the multi-tenant level: each school, district, or program gets its own logo, colors, domain, and email sender.
More questions? The full FAQ lives in the developer docs, from API auth and webhooks to eIDAS signature levels.
Evidence that holds up.
SOC 2 Type I · HIPAA compliant · ESIGN & UETA · eIDAS SES / AES · GDPR. Legally valid in 50+ countries and 60+ jurisdictions.