stuck? start here.

start without an account in chat or curl, within the bounded guest allowance. ask for what you want — "fold the BRCA1 protein", "dock imatinib against ABL1" — and .bloom* plans the run, executes it on real tools, and hands back the artifact: a structure file, a docking pose set, or an ADMET table. the web app, curl to /api/v1/orchestrate, the ivybloom terminal app and any MCP client all reach Ivy; a single tool job can also be dispatched directly with curl to /api/v1/jobs, ivybloom run, or a studio project. accounts add saved sessions, higher quota, and the full catalog.

all users can browse the public docs, workflow guides, and FAQ. free-tier users can submit support tickets with a 48-hour response target. paid plans include priority support with a 24-hour response target, and enterprise customers get dedicated technical contacts and custom onboarding sessions.

the guides page (/help/tutorials) groups maintained starting points by workflow. Each card opens the public documentation or recipe for the inputs, tools, and next step; use the full docs index when you need deeper reference material.

the compliance page (/help/compliance) states the current controls and readiness status for the frameworks it discusses, including 21 CFR Part 11, HIPAA, SOC 2, and GDPR. It distinguishes implemented controls from work in progress; enterprise plans add options such as audit logging, SSO/SAML, and self-hosting support.