Editions

Three ways to run Kaira.

Open, Community, and Chapter sort by who hosts the AI and where your data lives. They are independent of how you practice: solo, precepted, and program activation work inside any edition.

Tell us about your context

How the editions differ

The editions differ on one axis: where the AI runs and where your audio lives. Open is Kaira-hosted and free for individuals, with audio de-identified and dropped so only the narrative and its codings remain. Community is Kaira-hosted SaaS under a Business Associate Agreement, for schools, residencies, and community systems that do not run their own AI. Chapter is for organizations that have already certified their own AI infrastructure for PHI: Kaira runs as tools inside your runtime, your audio and transcripts never leave your tenant, and only de-identified signals flow back. Editions are orthogonal to activation modes. A student can be solo on an Open account or an unpaired user inside a Community tenant. Program activation always implies Community or Chapter.

The three editions

Pick the edition that fits where your data lives.

Most schools and health systems start on Community and move to Chapter once they have stood up their own PHI-certified AI runtime. Individuals stay on Open for free.

Open

Edition

Free, for any individual nurse.

Kaira-hosted on HIPAA-grade infrastructure, free for any individual nurse: student, new grad, preceptor, or educator. Audio and original transcripts are dropped after de-identification, so only the de-identified narrative and its codings are kept. Procedural Hands sub-competencies cap at Developing until a preceptor observes you, which is Benner's model of skill acquisition, not a paywall.

Who it's for
Any individual nurse: student, new grad, preceptor, or educator.
Activation default
Defaults to solo. You can invite a preceptor to pair up (precepted) inside Open.
Trust posture
Audio and transcripts are de-identified and dropped at capture. No employer can read your record.
This fits us

Community

Edition

Hosted by Kaira, under a BAA.

Kaira-hosted SaaS under a Business Associate Agreement, per-seat licensed, with data retention set by your own policy. Built for nursing schools, residencies, and smaller or community health systems that do not run their own AI infrastructure. Adds a Hands extension layer: your existing skills checklists (HealthStream, Cornerstone, and similar) are ingested as extension items on top of the AACN sub-competencies.

Who it's for
A nursing school, residency, or community health system without its own AI infrastructure.
Activation default
Defaults to program, with solo and precepted available in nested contexts.
Trust posture
BAA in place. Reflection content stays private and does not cross over to preceptor or institutional surfaces. Only de-identified signals do.
This fits us

Chapter

Edition

Greater customization, including your own AI runtime.

For large health systems, academic medical centers, public agencies, and organizations that have already certified their own internal AI infrastructure for PHI. MCP-native: Kaira's primitives run as tools inside your AI runtime, so audio and transcripts never leave your tenant. Only structured, de-identified signals flow back to Kaira. Adds Community-style extensions plus sector-specific configurations (Magnet-aligned, AACN-CCNP-aligned, specialty boards).

Who it's for
A large health system, AMC, or public agency with its own PHI-certified AI runtime.
Activation default
Program across the deployment, with solo and precepted nested inside it.
Trust posture
Customizable, for example if your organization has its own AI runtime, raw audio and transcripts stay in your closed system. Only de-identified codings, AACN PI states, divergence flags, and retention milestones flow back to Kaira.
This fits us

Open is the canonical AACN substrate. Community and Chapter extend it with employer-defined Hands depth using parent_extension_id and extension_owner provenance tags so the source of every Hands extension is always traceable.

Talk through the right edition for your context.

Most CNOs, L&D leaders, and residency directors start with a Community deployment scoped to one cohort, then move to Chapter once their own AI runtime is certified for PHI. Tell us which edition fits and we will walk through it with you.

Which edition fits your context?

We will reach out to walk through edition fit, data governance, and a scoped pilot. No sales sequence.