Compare progress to the IEP
Connect provider-created goals and progress evidence to original IEP goals, even when the wording differs.
Kesher means connection
Kesher connects schedules, services, IEP goals, documentation, progress, and reporting in one clear system, with AI features that support the work at every step.
The idea behind the platform
A successful IEP depends on dozens of people, decisions, documents, and deadlines moving together. Kesher gives every moving part one place to connect, from daily provider routines to school-wide oversight.
From fragments to flow
When plans, services, notes, goals, and deadlines live in separate places, teams spend too much time reconstructing context by hand. Kesher turns daily routines into a shared record designed to support compliant workflows.
One connected workflow
Capture the work once, where it happens, and keep the whole IEP journey visible without stitching it together by hand.
Swipe to explore the product preview
Jordan M.
Grade 6 · Active IEPIntelligence in the workflow
Kesher applies intelligence to the student context teams already maintain, helping providers document faster and leaders understand the work more clearly.
Connect provider-created goals and progress evidence to original IEP goals, even when the wording differs.
Create service-specific reports and lesson plans from relevant goals, notes, interventions, and curriculum context.
Compare structured assessments and uploaded files with session data to surface alignment and discrepancies.
Analyze documents against organization-defined criteria while giving administrators visibility into team AI use.
For school leaders
Connect daily provider activity to the school-wide visibility leaders need. Easily track completed sessions, missing documentation, contact history, goal progress, and upcoming work with customizable, intelligent reporting.
For special education providers
Kesher turns provider schedules into sessions, keeps notes beside the work, and carries interventions and progress into reporting. Enter information once, reduce administrative drag, and keep professional judgment at the center.
See what a connected workflow can look likeBuilt for work that matters
Kesher is designed for clarity at every layer, from daily provider workflows to the safeguards and technical details.
Sensitive data is encrypted in transit and at rest. Role-based access, audit logging, and regular security reviews help protect each organization's records.
Learn about our security practicesKesher AI runs through AWS Bedrock in Kesher's AWS environment. Customer data is not used to train shared or public models, access follows user permissions, and outputs require professional review.
Learn about our approach to AIKesher is FERPA compliant and follows New York State student data privacy laws. Access to customer data is governed by role-based permissions and limited to authorized access.
View privacy policyKesher targets WCAG 2.2 Level AA across its interfaces. Formal conformance details will be published after completion of an independent accessibility audit.
View accessibility statementKesher's API-first architecture connects student and workflow data with the systems each organization relies on, without requiring teams to work around a closed platform.
Discuss integrationsEvery customer can use the same public API that powers Kesher, with access included at no additional cost for the connections their workflows require.
View API docs API docs coming soonStart a conversation
Tell us a little about your school or organization. We will show you how Kesher can connect your teams, documentation, deadlines, and reporting.
Kesher / Privacy
This page provides the structure for Kesher's privacy policy. All language below is a placeholder and requires legal review before publication.
Placeholder for reviewed language describing information provided directly, product usage information, and information collected through the marketing site.
Placeholder for approved explanations of service delivery, communication, security, support, analytics, and legal obligations.
Placeholder for counsel-approved language addressing student records, school authorization, and applicable education privacy requirements.
Placeholder for reviewed language about vendors, subprocessors, legal requirements, and organizational changes.
Placeholder for approved retention practices and security safeguards. No unreviewed security or compliance commitments should be added here.
Placeholder for applicable access, correction, deletion, communication, and jurisdiction-specific rights.
Privacy contact and mailing details will be added before launch.
Effective date: To be determined
Kesher / Accessibility
Kesher is being designed so that school leaders, providers, and families can access the information and workflows they need.
Placeholder for an approved accessibility commitment and the scope of products, services, and content covered by this statement.
Placeholder for the target accessibility standards and the design, development, testing, and remediation practices used to support them.
Placeholder for tested browsers, operating systems, assistive technologies, and expected technical requirements.
Placeholder for transparent documentation of known barriers, available alternatives, and planned remediation.
Accessibility contact information and a process for requesting assistance will be added before launch.
Statement date: To be determined
Kesher / Security & AI
Kesher provides schools with role-based controls over sensitive student information and the AI-assisted workflows that use it.
Sensitive data is encrypted in transit and at rest. Role-based access, audit logging, and regular security reviews help protect each organization's records and limit access to authorized users.
Kesher is FERPA compliant and follows New York State student-data privacy requirements. Access is restricted through role-based permissions, including authorized organizational and service-administration access.
Kesher's AI features use AWS Bedrock within Kesher's AWS environment. Customer data is not used to train shared or public foundation models.
AI access follows each user's existing permissions. Permission controls restrict AI-assisted work to the records, features, and actions the user is authorized to access.
AI outputs must be reviewed by an authorized professional before use or inclusion in a student record. AI usage and conversations may be visible to authorized administrators of the customer organization for oversight.
Kesher conducts regular security reviews. Final documentation will provide reviewed details without claiming certifications or guarantees that have not been independently established.
Schools and organizations can request additional security and AI information as part of a Kesher conversation.
Start a conversationLast reviewed: Draft pending final approval
404 / Link not found