Skip to main content

Start with the outcome you want

Host AI agents. Connect them everywhere.

Pick your first AI workflow — then launch it with guided setup

Choose one useful outcome, launch it in a hosted agent workspace, and connect it to people over messaging and voice with guided tool setup. If you can describe what you want to happen, you can start here, then inspect, configure, connect, or take more direct control whenever it helps.

View product overview · See pricing

Hosted first, with room to grow

Choose the ChatInfra deployment path that fits

Whether you run a business or are working toward your own goals, the homepage presents the same Hosted ChatInfra handoff and safe-start journey. That handoff does not establish current public registration or paid self-service. ChatInfra Edge and ChatInfra Sovereign remain visible for qualified, contact-led conversations.

Hosted handoff

Hosted ChatInfra

The default hosted path, with a crawlable handoff to explore supported setup.

Explore Hosted ChatInfra

Contact-led

ChatInfra Edge

Talk with us about a qualified deployment closer to the systems and people it supports.

Discuss ChatInfra Edge

Contact-led

ChatInfra Sovereign

Talk with us about qualified deployment needs that call for greater infrastructure control.

Discuss ChatInfra Sovereign

One shared safe-start journey

A clear path from first outcome to confident expansion

Use this guide to launch a workflow for your business or for a project of your own. It describes the intent of a safe start, not a fixed onboarding interface or a promise about specific product screens.

  1. 1

    Choose one concrete outcome

    Name the useful result you want before choosing tools, channels, or a larger rollout.

  2. 2

    Start with one agent

    Give one focused agent a clear job so the first launch stays understandable and reviewable.

  3. 3

    Direct it, set boundaries, and connect only what is needed

    Teach the agent how to help, define its limits, and add only the tools or channels the outcome needs.

  4. 4

    Observe and refine behavior

    Review how the agent behaves in practice, then adjust its direction and boundaries.

  5. 5

    Expand as confidence and needs grow

    Add agents, connections, and autonomy only after the first behavior has been observed and refined.

Why teams can start safely

Start on rails, then turn the dial deliberately

ChatInfra keeps the first rollout scoped and reviewable, then states where the behavior sits on the on-rails to autonomous dial before teams expand it. Owners can start with guided support, then choose when to inspect configuration, connect more tools, or take more direct control.

On rails

Start with one safe workflow

Pick one useful outcome, keep the first launch scoped, and leave human handoff clear before expanding.

Dial

Know where autonomy sits

ChatInfra frames behavior as an on-rails to autonomous dial so every rollout can state how much freedom the agent has.

Worked example

Calbot is the on-rails worked example

Calbot is ChatInfra's appointment-making AI concierge for the hosted core. Its current production state and its WhatsApp messaging and Twilio voice channels require their own evidence.

Evidence boundaries

What the evidence does and does not establish

A hosted-core observation was recorded on July 14, 2026; it does not establish current public registration, first-party agent selection, checkout, trial creation, card collection, conversion, charging, or paid self-service. XMPP and JMAP account substrate plus WhatsApp messaging and Twilio voice connector implementations exist, but their availability is gated pending named evidence gates. Calbot’s current production state and channels require their own evidence.

Hosted core has a dated observation

The July 14, 2026 observation does not establish current public signup, first-party agent selection, or paid entry.

XMPP + JMAP substrate is implemented

Account-substrate implementations exist; availability is gated pending account evidence.

WhatsApp + Twilio connectors are implemented

Connector implementations exist; their availability is gated pending named evidence gates.

Roadmap stays marked coming

Roadmap-only channels and product lines are presented as coming until their status changes.

How ChatInfra supports that choice

Once you know the first outcome you want, the same core building blocks keep the launch reviewable and easy to explain to the rest of the team.

01

Hosted agent workspaces

A supported place to host, review, and improve the agent workflows you launch first.

02

Capability catalog

Outcome-driven, shareable capability pages that explain what each agent can do before setup starts.

03

Tool setup support

Guided help connecting calendars, contacts, and tools safely around the first workflow.

04

Messaging + connectors

Implemented WhatsApp messaging and Twilio voice connectors with gated availability, plus roadmap channels marked coming.

How it works

  1. 1
    Start with a goal

    Pick the first outcome you want to launch and the guide, integration, or support path that fits it.

  2. 2
    Connect channels + tools

    Add messaging connectors and tools only where they help the first workflow. Keep it minimal at first.

  3. 3
    Launch and iterate

    Use a hosted agent workspace to refine behavior, keep human handoff, and expand once the rollout is stable.