Documentation
Documentation for evaluating Homany - not just using it
Homany is a platform with a real operational surface: an API, an MCP server for agents, and a security posture you can review. These pages are the entry point for technical evaluators and developers.
Start here
Where to go
API & MCP
The operational surface agents and integrations act on - sheets, tasks, views, webhooks - and how MCP exposes it to agents.
See the APISecurity documentation
Hosting and data-handling posture, what you can review, and how to request a deeper assessment under NDA.
Review securityGuides & references
Practical material on sovereign work, agent-ready operations, and usage-based pricing in the resource library.
Browse the libraryProduct walkthrough
How the workspace, agents, deployment, and security fit together, from the product pages.
See the product
For technical evaluators
How to evaluate Homany technically
A short path for a technical reviewer to confirm depth before committing time to a pilot.
- 01
Check the operational surface
Confirm the API and MCP cover the objects your workflows depend on - sheets, tasks, columns, views, comments, webhooks - so automation and agents have something real to act on.
- 02
Confirm agent-readiness
Verify agents act through the same surface as the API, with scoped permissions and an audit trail - not a separate, weaker path.
- 03
Map the deployment model
Decide which posture you'll run - managed sovereign cloud, your tenancy, or on-prem - and confirm the capability you need exists there.
- 04
Review the security posture
Read the security docs, then request a deeper review for the specifics your risk team needs.
Full developer docs
Deeper reference and API documentation live here on-site for now, and may move to a dedicated docs domain as the surface grows. These entry pages stay the same either way.
Evaluating Homany's technical depth?
Book a working session with our team to walk the API, agent model, and deployment options for your environment.