Is Odysseus AI only for local models?
No. The product story is private by default: teams can connect local models, hosted endpoints, and internal tools while keeping control over data flow.
Docs
Quickstart for a private AI workspace.
This public docs page gives buyers and builders a concrete path before auth, checkout, or product onboarding are connected.
Get started
- 1. Create a workspace for one project or team workflow.
- 2. Connect the model endpoints your organization already trusts.
- 3. Add MCP tools for files, docs, email, and internal systems.
- 4. Run a research or agent workflow and compare model outputs.
- 5. Save durable memory only for facts the team wants reused.
Integrations
Start with model endpoints, MCP servers, local documents, research sources, and email workflows.
Privacy
Treat private context as a controlled workspace asset, not a default payload for every external model.
Operations
Keep agent plans, tool traces, research outputs, and model comparisons visible enough for team review.
FAQ
Questions before the product path is connected.
These answers keep the first public website honest while the product onboarding remains a static route.
Does the first version include checkout or auth?
No. The marketing site uses static CTA routes only. Pricing buttons lead to the quickstart section until product onboarding is connected.
What makes it different from a generic chatbot?
Odysseus AI is positioned as a workspace: agents, tools, memory, research, model comparison, and email live in one operational surface.