What changes between plans?
Plans differ by size and use, such as by the number of available seats, the volume of available sources, the administrative controls, and enterprise agreements.
Private founding-cohort accounts begin with a 14-day trial for authorized non-PHI use after the controlled signup lane admits a valid one-time access code. No credit card is required to create the account or start the trial after admission.
Checking private founding-cohort availability.
In the future, we hope to deploy a free plan once we cover costs of operations.
Program and institutional use is not self-service. It requires a controlled non-PHI scope review and does not imply paid-deployment or PHI readiness.
Plans differ by size and use, such as by the number of available seats, the volume of available sources, the administrative controls, and enterprise agreements.
Yes. The Resident plan is the authorized individual lane for one clinician using a focused, non-PHI rotation library. Team and Program plans add shared access and administration.
A seat is one user who can access shared projects, ask questions, review sources, and inspect cited answers.
MARCUS extracts, chunks, and embeds approved documents so it can retrieve relevant passages and generate cited responses. Approved document text and queries may be processed by configured model and embedding providers. Provider retention, training-use, residency, and account-control claims are deployment-specific and require current evidence; MARCUS does not make a categorical no-training promise here. Review our terms and privacy notice for the current boundary.
MARCUS is not intended to be used for specific patient health information (PHI). Current individual and institutional lanes are strictly non-PHI and have no contract or authorization for PHI use. Any future PHI program would require a separate legal, privacy, security, provider, deployment, and institutional approval process. For background, review HHS guidance on de-identification.
Individual accounts begin with guided non-PHI onboarding. Institutional pilots require a written plan covering source classification, named access, custody settings, processing checks, answer-quality review, incident ownership, and closeout.