Skip to content
AlumiaDocs

Search docs

Find pages, headings, and concepts. Press ⌘K or Ctrl+K to toggle.

Enterprise intake and deployment targets

Request an enterprise demo, understand the inquiry API, and see how tenant deployment targets are prepared.

Open in ChatGPTOpen in Claude

Use this guide when a team needs a dedicated Alumia rollout conversation rather than the self-serve path. It covers the public /enterprise form, the inquiry API behind it, and the deployment target concepts operators use after qualification. It does not require or expose internal-only secrets.

1. Submit the public enterprise form

Open /enterprise. The page explains the enterprise rollout motion and shows a demo request form with:

  • name
  • company
  • work email
  • use case

Submit the form with a real business use case. The page sends the request to POST /api/v1/enterprise-inquiry and shows a success state when the request is accepted.

The form also includes a hidden website field as a honeypot. Real users leave it blank; automated spam that fills it is accepted with no email side effect.

2. Know what the inquiry API accepts

The public endpoint is:

POST /api/v1/enterprise-inquiry

It accepts JSON:

{
  "name": "Ada Lovelace",
  "company": "Example Corp",
  "email": "ada@example.com",
  "useCase": "We want agents to support enterprise operations.",
  "website": ""
}

Validation requires name, company, a valid email, and a useCase of at least 10 characters. Successful requests return 202 Accepted.

The route is rate-limited to 5 requests per minute per IP and sends the inquiry to the configured enterprise inbox. If no inbox override is configured, the default recipient is enterprise@alumia.com.

3. Understand deployment target planning

Enterprise customers can run on a host-based tenant target such as:

https://<org>.enterprise.alumia.com

Deployment targets track the pieces operators need before cutover:

  • the deployment target name, such as enterprise-acme
  • the default enterprise host and any custom domains
  • routing mode and isolation mode
  • provisioning, route, backup, and health status
  • DNS verification records and certificate status
  • migration version and cutover approval state

Admins review this from deployment target operations rather than from the public inquiry form. Public inquiries start the conversation; deployment targets represent the provisioned runtime destination after the tenant is approved.

4. What to share with the customer

Send customers the public form link and ask for enough context to size the rollout:

  • expected number of seats and workspaces
  • security, SSO, and audit requirements
  • data residency or custom domain needs
  • launch timeline and pilot success criteria

Do not send internal provisioning commands, secret names, Terraform workspace names, or private environment variables. Keep customer-facing guidance at the form, inquiry status, and deployment target overview level.