Pricing

Pricing built around the work, not the headcount

CT Networks is priced around event workspaces and the AI event team that runs them. We don't bill on attendees, we don't bill on raw API usage, and we don't bill operators per integration.

Priced per event workspace

Each event your team runs gets a dedicated workspace, an AI event team, and the playbooks, automations, and command-center access that come with it.

Operator seats, not headcount

Pricing scales with the operators who run the event, not the people who attend it. Attendees are never billed.

Implementation when it's needed

Implementation support is available for event teams that want help connecting integrations, building runbooks, and tuning playbooks for their specific operating model.

How we work with event teams today

Pilot

One event, one workspace, one AI event team.

For event teams running their first CT Networks event end to end.

  • One event workspace
  • Up to 4 AI coworkers
  • Core playbook library
  • Command center for the operator team
  • Approval queue and audit trail
Talk to us about a pilot

Operating team

Recurring events with a stable AI event team.

For event teams running multiple events a year with shared operators.

  • Multiple event workspaces
  • Full coworker taxonomy
  • Automations and scheduled routines
  • Reusable playbook and runbook library
  • Operator role-based permissions
Talk to us about your event calendar

Festival scale

Large or complex events with multiple operating tracks.

For festivals, conferences, and summits with concurrent operating teams.

  • Concurrent workspaces with shared knowledge
  • Custom integrations into your event stack
  • Implementation support and runbook authoring
  • Dedicated command-center configuration
  • Custom approval and audit policies
Talk to us about a custom engagement

We don't publish a price list yet

CT Networks is in the early customer stage. Pricing is set collaboratively with the first event teams we work with so the workspace, coworker team, and integration scope match the actual event you're running. The fastest path to a number is a conversation.