The Auzi product
The app is the part families and staff carry. Behind it is one reusable platform for managing public information, approved AI knowledge, secure role-based access, and school operations.
Four connected layers
Every layer builds on the one before it. The app never arrives without the tools your staff need to keep it useful.
Mobile product view
The mobile view compresses the product architecture into tabs so school leaders can jump directly to the layer they are evaluating.
01 · Mobile app
Alerts, calendars, directories, forms, handbooks, links, and trusted answers live in a fast, branded iOS and Android experience. The public app is designed for information that does not require a private student record.
School-owned identity, fast paths to high-use information, normal push volume, and public AI grounded in approved content.
02 · Included Admin Console
Authorized staff use the browser-based Admin Console to publish content, send notifications, manage calendars and resources, organize approved AI sources, and control administrator access.
Your school manages the information. Auzi maintains the reusable software and contracted releases.
03 · Auzi Portal
Your school receives its own branding, content, navigation, administrators, knowledge sources, and permissions inside the shared Auzi platform.
Standard deployments are configured, not rebuilt from scratch.
04 · Operations
Add repeatable requests and approvals, audit controls, reporting, SSO, standard integrations, multi-campus administration, and scoped custom modules.
Standard modules stay predictable. Bespoke work is scoped before development.
01 · Mobile app
Alerts, calendars, directories, forms, handbooks, links, and trusted answers live in a fast, branded iOS and Android experience. The public app is designed for information that does not require a private student record.
02 · Included Admin Console
Authorized staff use the browser-based Admin Console to publish content, send notifications, manage calendars and resources, organize approved AI sources, and control administrator access. It is included with every branded app.
Your school manages the information. Auzi maintains the reusable software and contracted releases.
Public and private
Public calendars and resources should remain simple to reach. Private information belongs behind a school-configured role and login boundary.
General calendars, policies, forms, directories, enrollment information, and approved public AI knowledge can stay open to the school community.
Connected adds private resources and authenticated AI whose content and tools can change by school and role.
03 · Auzi Portal
Your school receives its own branding, content, navigation, administrators, knowledge sources, and permissions inside the shared Auzi platform. Standard deployments are configured—not rebuilt from scratch.
04 · Operations
Add repeatable requests and approvals, audit controls, reporting, SSO, standard integrations, multi-campus administration, and scoped custom modules.
Standard modules stay predictable. A bespoke workflow, dashboard, integration, or module is scoped separately before development.
School-specific AI
Public assistants can help families find calendars, policies, forms, and resources. Authenticated assistants can be limited by school and role when private access is part of the plan.
Auzi separates public knowledge from authenticated/private contexts. Standard AI use is defined in scope; the site does not promise unlimited use.
A practical next step
Tell us what your school needs. We’ll show the right plan and any optional costs before you move forward.