How a venue or hospitality project works at Autotelic

Build sequence

1. 1. Feasibility

   Released

   A venue technology project starts with a scoped consult; a client venue's rooms, meanwhile, are bookable without waiting on that consult.

   Book a scoped consultBack to Feasibility

2. 2. Booking

   Released

   A client venue's rooms hold and pay the same way any fixed-price SKU does — a real hold, a real Stripe pay page.

   Book a venue roomBack to Booking

3. 3. Estimate

   In progress

   Self-serve venue pricing is in build; a scoped consult prices a venue technology project today.

   Get a venue project pricedBack to Estimate

4. 4. Edge compute

   Released

   The venue's look and feel runs on a venue operating system Autotelic built and maintains — staff app, message broker, room agents, and a power-recovery orchestrator.

   One 04:45 power-recovery run: agents and receivers back, doctor count, no text sent.

   Trigger

   Daily run at 04:45 (also on every headend boot, two minutes after startup); 45-minute cap.

   Wake the fleet

   Magic packets from the headend to every playout and TV agent: 25 of 25 agents online within about 5 seconds on the…

   Receivers

   DirecTV receivers powered: 8 of 8 on.

   Fleet doctor

   Health check across the room stack: failures went from 5 to 4 (one projector agent had not been running after its PC…

   Report and text

   Report retained for the staff app's Ready tab. Owner text skipped: the rule is worse-only for routine runs (a newly…

   Not in v1

   Sonos regroup, DirecTV retune, TV input fixes, agent restarts, headend reboot, and any volume or mixer write are…

   Show the raw response

   {
    "context": "After the 2026-08-18 venue-wide power loss left the headend and about 27 playout mini-PCs dark for 32 hours, the recovery was automated: every boot and every morning the orchestrator wakes the fleet, checks audio, powers the receivers, runs the fleet doctor, and texts the owner only when the picture is worse than the last report.",
    "steps": [
     {
      "step": 1,
      "label": "Trigger",
      "detail": "Daily run at 04:45 (also on every headend boot, two minutes after startup); 45-minute cap."
     },
     {
      "step": 2,
      "label": "Wake the fleet",
      "detail": "Magic packets from the headend to every playout and TV agent: 25 of 25 agents online within about 5 seconds on the 2026-09-05 run (on the first live run the night before, the headend's own wake packets brought back one basement screen that had been off)."
     },
     {
      "step": 3,
      "label": "Audio",
      "detail": "The house audio interface is resolved by friendly name, not by a hardware id that changes after a power event; status: decoding."
     },
     {
      "step": 4,
      "label": "Receivers",
      "detail": "DirecTV receivers powered: 8 of 8 on."
     },
     {
      "step": 5,
      "label": "Restore sources",
      "detail": "Skipped by design on daily runs; after a boot, only screens whose agent has heartbeated and whose state differs are re-commanded. Screens a human set to another source are never touched."
     },
     {
      "step": 6,
      "label": "Fleet doctor",
      "detail": "Health check across the room stack: failures went from 5 to 4 (one projector agent had not been running after its PC was powered on; started by hand later that morning)."
     },
     {
      "step": 7,
      "label": "Report and text",
      "detail": "Report retained for the staff app's Ready tab. Owner text skipped: the rule is worse-only for routine runs (a newly missing agent or a higher doctor failure count); boots and failed steps always text."
     }
    ],
    "doesNotDo": "Sonos regroup, DirecTV retune, TV input fixes, agent restarts, headend reboot, and any volume or mixer write are deliberately outside v1.",
    "openItems": "A rehearsed headend reboot in a quiet window; three basement screens off the network on the panel side; the projector agent's autostart."
   }

   Talk to us about edge computeBack to Edge compute

5. 5. Project management

   Released

   A larger venue technology project moves into the client portal the same way any other project does.

   Ask about the client portalBack to Project management

6. 6. Field

   Internal

   The crew cockpit app manages venue installs on site, shown here but never linked as something to install.

   Back to Field

Rooms on the schedule

I'm a venue — start from the purpose:

• Play, sing, watch
• Sell & serve