Local / Desktop reference architectureAdmissions inquiries
A Local / Desktop reference architecture for admissions inquiries in Education. Triggered by applicant or student inquiry received, Padiso orchestrates 3 specialist agents on Claude Code + Ollama, on your machines, reaching student information system (sis) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
Local / DesktopRuntime: Claude Code + Ollama, on your machinesTrigger
Applicant or student inquiry received
Education
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Claude Code + Ollama, on your machines
Admissions agent
agent
Student services agent
agent
Operations agent
agent
Integrations · MCP
MCP gateway
Your systems
Student Information System (SIS)
CRM
Document store
How the data flows
Trigger: Applicant or student inquiry received
- 1
Admissions agent answers questions and tracks the application status
- 2
It collects missing documents and updates the SIS
- 3
Routine cases proceed; exceptions route to staff
- 4
Decisions and records changes require approval
Agent team
- Admissions agent
- Student services agent
- Operations agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Claude Code + Ollama, on your machines
Student Information System (SIS)
CRM
Document store
Security & operational considerations
- FERPA-aligned access controls
- Student PII handled per policy
- Approvals on records changes
Local / Desktop deployment
Self-hosted: agents and models run on your machines, so regulated data and credentials never leave your network. Best when data residency is non-negotiable.
Run this blueprint anywhere
More Education blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.