LOCAL HOSTING AUDIT — what runs on your Windows box right now

Date: 2026-05-07

Scope: every public URL/service in the TITAN + Innerverse + LiveGrow stack, broken down by where the actual code/data lives.

---

TL;DR — One-line answer

Two pieces are served from local right now:

1. Cloudflare Tunnel titan — local TITAN service exposed publicly at 4 hostnames on livegroweveryday.com

2. TITAN brain itself (memory, agents, scripts, scheduled tasks, .env) — never serves to the internet, but every cron/agent action originates here

Everything else (Innerverse apps, LiveGrow apps, nightly content generation) runs on AWS.

---

1. Public URLs — by hosting source

1A. Hosted ON LOCAL (via Cloudflare Tunnel)

| URL | Backed by |

|---|---|

| https://livegroweveryday.com/ (apex) | Local TITAN service via tunnel titan |

| https://www.livegroweveryday.com/ | Local TITAN service via tunnel titan |

| https://api.livegroweveryday.com/ | Local TITAN service via tunnel titan |

| https://titan.livegroweveryday.com/ | Local TITAN service via tunnel titan |

| https://titan-dashboard-proxy.harnoors.workers.dev/ | Cloudflare Worker (edge) — proxies to one of the above? |

The mechanism: a cloudflared daemon runs on your Windows machine, holds an outbound connection to Cloudflare. When anyone hits one of those 4 hostnames, Cloudflare pipes the request through the tunnel into your local TITAN service. If your machine is off, those 4 URLs go dark.

The Cloudflare Worker titan-dashboard-proxy is JS code running at the edge; we don't yet know what it proxies — paste its source to find out.

1B. Hosted on AWS (no local dependency)

| URL | Hosting |

|---|---|

| https://dreams.silentinfinity.com/ | S3 + CloudFront + Route 53 |

| https://oracle.silentinfinity.com/ | S3 + CloudFront + Route 53 |

| https://timelines.silentinfinity.com/ | S3 + CloudFront + Route 53 |

| https://childhood.silentinfinity.com/ | S3 + CloudFront + Route 53 |

| https://arsenal.silentinfinity.com/ | S3 + CloudFront + Route 53 |

| https://apps.silentinfinity.com/ | S3 + CloudFront + Route 53 (Innerverse hub) |

| https://assistant.livegroweveryday.com/ | S3 + CloudFront (DNS via Cloudflare) — pending CNAME paste |

| https://outfit.livegroweveryday.com/ | same — pending CNAME paste |

| https://dinner.livegroweveryday.com/ | same — pending CNAME paste |

| https://wallet.livegroweveryday.com/ | same — pending CNAME paste |

| https://move.livegroweveryday.com/ | same — pending CNAME paste |

| https://apps.livegroweveryday.com/ | same — pending CNAME paste (LiveGrow hub) |

These serve from S3 directly — your Windows box can be off for a year and they keep serving fine.

---

2. Cron / scheduled jobs — by execution source

2A. Running ON AWS

| Job | Schedule | Where |

|---|---|---|

| innerverse-nightly Lambda | cron(0 7 ? *) (03:00 ET) | EventBridge rule innerverse-nightly-3am-et → Lambda — generates fresh dreams/oracle/childhood content, writes to S3 |

That's it. One thing.

2B. Running ON LOCAL Windows

These all live in F:/TITAN/scheduled-tasks/ and are triggered by Windows Task Scheduler / TITAN's own scheduler:

| Task | What it does |

|---|---|

| agentic-247-watchdog | 24/7 watchdog for stuck agents |

| claude-code-audit-every-6h | Audits Claude Code state every 6h |

| job-search-daily-digest | Daily digest of job postings |

| nightly-report-writer | Writes nightly TITAN report to auto-memory/ |

| swarm-health-orchestrator | Health-checks the agent swarm |

| titan-batch-poll-15m | Polls Bedrock async batch jobs every 15 min |

| titan-daily-newsletter | Sends the daily TITAN brief email via SES |

| titan-daily-pa-email | Personal-assistant style daily email |

| titan-daily-token-audit | Audits token spend across providers |

| titan-inbox-watch | Watches Gmail inbox for triggers |

| titan-master-batch-nightly | Master orchestration of nightly batch |

| titan-weekly-reminder | Weekly reminders |

| (legacy) local Innerverse nightly cron | Likely still scheduled — duplicate of the new Lambda; safe to disable |

All of these stop if your Windows box is off.

---

3. Brain / state — by location

3A. Local-only (will never move per your direction)

F:/TITAN/server/.env — all API keys (authoritative copy)
F:/TITAN/knowledge/auto-memory/ — auto-memory index, feedback files, nightly reports
F:/TITAN/knowledge/personal/ — personal journals, anything you've marked private
F:/TITAN/agents/ — sub-agent definitions (SCOUT/VAULT/FORGE/GUIDE/ORACLE/DARWIN)
F:/TITAN/skills/ — skill markdown files (/feed, /dream, /evolve, etc.)
F:/TITAN/scripts/ — every Python script
F:/TITAN/plans/ — strategy docs, advisor memos, app source HTML
F:/TITAN/state/ — local app state

3B. On AWS

S3 innerverse-voice-scratch/ — pre-rendered nightly content for Innerverse + static HTML for LiveGrow
AWS Secrets Manager (3 secrets, all innerverse/*) — copies of OpenAI key, ElevenLabs key, ElevenLabs voice ID — only used by the Lambda
CloudWatch Logs — Lambda execution logs

---

4. What "going fully off Cloudflare" requires

Right now Cloudflare provides:

1. DNS authority for livegroweveryday.com (also a Route 53 hosted zone exists but is not authoritative)

2. Tunnel terminating 4 public hostnames into your local TITAN service

3. A Worker (titan-dashboard-proxy) running edge JS

To eliminate Cloudflare:

| Step | What's needed |

|---|---|

| 1. Migrate the local TITAN service | Move whatever's behind the tunnel onto AWS App Runner (always-on, ~$25/mo for tiny container) or Lambda + API Gateway (cheaper if request/response only). Need to know what the local service is first — likely a Python web server. |

| 2. Replace the Worker | Rewrite titan-dashboard-proxy as either CloudFront Functions (if simple), Lambda@Edge, or another API Gateway+Lambda. Need its source code first. |

| 3. Flip nameservers | aws route53domains update-domain-nameservers — one CLI call. Domain is registered with Route 53 Domains so no registrar lock-in issue. |

| 4. Recreate DNS records in Route 53 | Apex + www + api + titan now point at the new AWS-hosted service; assistant/outfit/etc point at CloudFront. |

Ballpark new cost: $25–60/mo additional (App Runner is the biggest line item; Lambda + S3 + CloudFront stay near-free at this volume).

---

5. Specific things still to do (in order)

1. ✅ AWS Lambda nightly batch — DONE (live as of today)

2. ⬜ Paste the 6 LiveGrow CNAMEs into Cloudflare → LiveGrow apps go live on *.livegroweveryday.com

3. ⬜ Disable the local Innerverse nightly cron (duplicate of Lambda — burning electricity for nothing)

4. ⬜ Delete the 5 disabled CloudFront distros (~15 min after disable propagates)

5. ⬜ Identify what local service the Cloudflare Tunnel titan points at (paste your ~/.cloudflared/config.yml or run cloudflared tunnel info titan)

6. ⬜ Identify what the titan-dashboard-proxy Worker does (paste its JS source)

7. ⬜ Migrate (5) and (6) to AWS, then flip nameservers from Cloudflare to Route 53

8. ⬜ Rotate OpenAI + ElevenLabs API keys (they were pasted unscoped earlier; replace with restricted versions)

---

Author: TITAN

Generated: 2026-05-07