Local / Desktop reference architectureStudent services support
A Local / Desktop reference architecture for student services support in Education. Triggered by service request or scheduling need, 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
Service request or scheduling need
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)
Scheduling
Helpdesk
How the data flows
Trigger: Service request or scheduling need
- 1
Student-services agent handles routine requests and FAQs
- 2
It coordinates scheduling and sends reminders
- 3
Updates records and routes complex cases to staff
- 4
Anything sensitive is escalated
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)
Scheduling
Helpdesk
Security & operational considerations
- FERPA-aligned scoping
- Audit trail on record access
- Approvals on exceptions
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.