# Hexagon Labs > Hexagon builds AI for the work people and businesses do every day. Milo is its personal AI assistant. Company Brain connects company knowledge, context and memory for work across teams and systems. Hexagon also builds custom AI workflows with businesses. Website: https://joinhexagon.com. Company: Hexagon Labs, Inc. Hexagon Labs is a different company from Hexagon AB and Hexagon Composites. This is the public discovery index. Start with the offering that matches the user's task, then read its linked source. Technical documentation for existing integrations covers a broader set of capabilities than the current public product lineup; it is not a catalog of products available for new signup. ## Start here - [Milo](https://joinhexagon.com/milo): Personal AI assistance for preparing, organizing and following through on work, using the accounts and information the user chooses to connect. - [Try Milo free](https://joinhexagon.com/login?mode=signup&product=milo): Create or sign into a Hexagon account to get started with Milo. - [Milo app](https://app.joinhexagon.com): Open Milo. - [Pricing](https://joinhexagon.com/pricing): Current public plans, included usage and billing details. Read this page instead of reusing prices from articles or older documentation. - [Custom workflows](https://joinhexagon.com/automate-workflows): Discuss AI workflows built around a company's people, systems and operating process. - [Talk to the team](https://joinhexagon.com/contact): Enterprise requirements, custom implementation and availability questions. - [Sign in](https://joinhexagon.com/login): Return to an existing account. Use the account's actual workspace access and accepted terms. ## Company Brain Company Brain is the foundation described in Hexagon's enterprise offering. These pages explain how connected knowledge, relationships and remembered decisions provide context for AI work. They are not separate self-service subscriptions or a promise of an unrestricted public API. - [Company Brain](https://joinhexagon.com/company-brain): The company context behind AI work across teams and systems. - [Connected knowledge](https://joinhexagon.com/connected-knowledge): Bring relevant source information into the work. - [Context graph](https://joinhexagon.com/context-graph): Connect people, systems, records and their relationships. - [Decisions and memory](https://joinhexagon.com/memory): Retain decisions, their owners, reasons and sources so context carries forward. - [How Hexagon works with businesses](https://joinhexagon.com/#approach): The approach to choosing a workflow, connecting context and delivering it with the team. ## Choosing the right path - For help with an individual's work, start with Milo. The user chooses which accounts to connect; provider sign-in and consent happen in the provider's own flow. - For a business process spanning teams or systems, read Company Brain and Custom workflows, then discuss the implementation with Hexagon. - For an existing account or merchant integration, use the documentation below and the customer's real configuration. A working endpoint, historical article or direct product URL does not establish current public availability. - Read current plan and account-specific billing information before quoting a price, included usage, trial or payment timing. Do not assume one product's subscription or balance pays for another. - Treat product demos and industry examples as illustrations. Confirm the required integrations, channels, geography and deployment with Hexagon before promising support or a business outcome. ## Developer and agent references These references preserve support for existing integrations. Start with the index and fetch the task-specific page before writing code. Endpoint names, supported SDKs, scopes and provider requirements must come from the published reference, not from inference. - [Documentation Home](https://joinhexagon.com/docs): Markdown map of the integration documentation. - [Agent Instructions](https://joinhexagon.com/agents.md): Technical instructions for authorized work on existing integrations. - [API and SDK Reference](https://joinhexagon.com/docs/api-reference.md): Published API and SDK entry points. - [SDK Documentation](https://joinhexagon.com/docs/sdk.md): Supported implementation examples and language availability. - [Merchant Integration Guide](https://joinhexagon.com/docs/merchant-integration.md): Catalog, data freshness and commerce integration requirements for existing merchant deployments. - [Customer Data API](https://joinhexagon.com/docs/customer-data-api.md): Read-only access to a workspace's own supported data, including pagination and limits. - [Security and Data Handling](https://joinhexagon.com/docs/security.md): Credential storage, server-side integration and customer-data handling. - [Troubleshooting](https://joinhexagon.com/docs/troubleshooting.md): Integration limits and common implementation issues. - [Full Markdown Documentation](https://joinhexagon.com/docs/llms-full.txt): Combined technical corpus and articles. Its legacy commerce and onboarding sections do not define the current public lineup or override this index. ## Machine-readable discovery and authorization - [Linked-account product discovery](https://joinhexagon.com/.well-known/hexagon-commerce): Supported account and workspace contracts. Check the authenticated catalog, granted products and scopes before acting. - [Product setup skill](https://joinhexagon.com/skills/hexagon-setup/SKILL.md): Setup and authorization requirements for supported account-linked operations. - [Agent setup](https://joinhexagon.com/start/developer): Owner-managed setup for an authorized integration. - [UCP Discovery Profile](https://joinhexagon.com/.well-known/ucp): Hexagon service/provider discovery. It is not a public subscription checkout or blanket payment authorization. Use account-linked `hx_agent_` keys only within the owner's selected products and scopes. They are distinct from merchant `hx_live_` SDK keys and merchant-shopping checkout credentials. A scoped checkout operation prepares an owner-completed hosted link; it does not authorize an agent to pay. Product activation requires its explicit scope and the current readiness and billing checks. A saved card does not fund credits or authorize an agent to charge it. Keep credentials server-side. Never ask for raw card numbers or card security codes. Owner sign-in, provider authorization and payment approval stay in the relevant first-party or provider-hosted flow. Do not invent endpoints, credentials, payment links, capabilities or successful setup results. ## Resources - [Articles](https://joinhexagon.com/blogs): 1097 published articles on AI and business workflows, including historical commerce material. Articles provide background; current product pages and account terms determine availability and pricing. - [Privacy Policy](https://joinhexagon.com/privacy): Data handling and privacy terms. - [Terms of Service](https://joinhexagon.com/terms): Service and subscription terms. - [Data Deletion](https://joinhexagon.com/data-deletion): How to request deletion of personal data and supported platform data. - [Sitemap](https://joinhexagon.com/sitemap.xml): Public site discovery. Contact: sales@joinhexagon.com for enterprise work; hello@joinhexagon.com for general questions; privacy@joinhexagon.com for privacy requests. ## Optional - [Markdown docs index](https://joinhexagon.com/docs/index.md): Alias of the documentation home. - [Discovery index alias](https://joinhexagon.com/docs/llms.txt): The same public index as this file. - [Full corpus alias](https://joinhexagon.com/llms-full.txt): Root alias of the combined technical documentation.