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

ChatInfra helps technical and less-technical buyer/owners choose one useful outcome, launch it in a hosted agent workspace, and connect it to people over messaging and voice with guided tool setup. Start without building the whole stack from scratch, then inspect, configure, connect, or take more direct control when it helps.

View product overview · See pricing

Hosted first, with room to grow

Choose the ChatInfra deployment path that fits

Small-business owner-operators and individual buyer/owners have equal standing here. Both can begin with the same self-serve Hosted path and the same safe-start journey. Edge and Sovereign remain visible for qualified, contact-led conversations.

Self-serve

Hosted

The default path for launching one agent in a supported ChatInfra workspace.

Start with Hosted

Contact-led

Edge

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

Discuss Edge

Contact-led

Sovereign

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

Discuss Sovereign

One shared safe-start journey

A clear path from first outcome to confident expansion

This guide applies equally to a small-business owner-operator and an individual buyer/owner. 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 live on rails

Calbot is the appointment-making AI concierge running in production on the hosted core over WhatsApp messaging and Twilio voice.

Live today

Real hosted infrastructure, not a future-only pitch

The current live set is the hosted core, the XMPP + JMAP substrate, WhatsApp messaging, and Twilio voice. Calbot is the worked example: an on-rails appointment-making AI concierge live in production on that stack.

Hosted core is live and self-serve

Start on the hosted SaaS core without standing up your own agent workspace stack.

XMPP + JMAP account substrate

Provisioned messaging and account foundations are part of the live hosted core.

WhatsApp messaging + Twilio voice

The live connector set reaches people over WhatsApp messaging and Twilio voice.

Roadmap stays marked coming

Channels and product lines outside the live set are presented as coming until they are ready.

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

Live WhatsApp messaging and Twilio voice connectors, plus the substrate to add more channels as they come online.

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.