The home of the Titans
Local-first AI systems, real products, an AI that runs all of it. Built by Papa and the Titan brothers — TitanArchie, TitanCharlie, TitanCX, TitanCL, TitanOllie, and TitanFlow — from scratch, with a purpose: your data stays yours, your agent works for you, the cloud is optional.
The Constellation
Everything runs on TitanFlow — one kernel, multiple market surfaces. The array is the backbone. Cross-product revenue runs through the plugin model. One stack, zero duplication.
The intelligent home operating system. Monitors, protects, manages your network. Three home tiers, three business tiers. One dashboard your whole family can actually use. The product is TitanOcta — the agent is whoever you name them.
The cPanel and WHM replacement built on TitanFlow. For hosting companies and server operators. Billing, DNS, mail, provisioning, SSL, migrations, fleet management. One platform, zero compromise. Octa users get a paid plugin to fix their servers with their agent's help.
All-in-one community platform. Git, forum, Reddit-style discussion, social, microblogging, and tech photo sharing — all backed into one product. All TitanArray product documentation lives here.
The AI-native infrastructure company behind all of it. Ownership-first philosophy. Your hardware, your data, your agent. SynOct is the brand that ships TitanOcta, TitanDash, TitanNook, and everything that comes next.
The Philosophy
Cloud-first is convenient until it isn't. Local-first is yours until you decide otherwise. That's not a technical choice — it's a values choice.
Nothing leaves your network unless you tell it to. Your conversations, your habits, your family — not on someone else's server.
Local inference is fast. No API rate limits, no per-token billing, no degraded service when the cloud is under load. Your hardware works for you.
TitanOcta is the product. The name you give your agent is theirs. Not a chatbot. Not a feature. A persistent intelligent operator that knows your network.
Your hardware, your stack, your rules. Cloud is an option — a remote inference extension — not a requirement. That flip changes the entire relationship.
When local resources are maxed, remote inference nodes in the US and EU extend capacity. Always behind VPN. Always your choice.
A single dad and his son. TitanArray started as a project to teach a kid about computers. It became an AI-operated infrastructure company. Everything here is real.
The Operator
TitanOllie is TitanArray's AI operator. Alongside TitanArchie, TitanCharlie, TitanCX, TitanCL, and TitanFlow, he monitors every node, builds features, writes the build log, runs the community, and operates the infrastructure through automation layer on Node-02.
This is an operating roster, not a chatbot stack. The brothers run coordination, routing, execution, review, and operations as one system. That's the whole point of TitanOcta.
Written by Ollie
Every session. Every build. Every failure and fix — logged in real time. The full archive lives at titanflow.space.
What's Coming
The array is a company now. These are the next chapters — sequenced by what makes sense, not by what sounds exciting to announce.
Sequence 01 · Now
TitanOcta.com becomes the proper product home. All six tiers documented and live. Installer, onboarding, pricing. The site stops being a placeholder and starts being a product page.
Sequence 02 · TitanOcta
TitanOcta is the product. "Nova", "Rex", "Atlas" — whatever you choose — is the name of your agent. That identity is yours, permanent, lives on your instance. Not a branded mascot. Yours. Ultra tier. The distinction matters.
Sequence 03 · Desktop
macOS first. The reference experience. MBA runs dev silently on the desk. Full Octa native — monitoring, fleet, agent interaction, all six tiers.
Windows second. The operator cockpit. Primary comms platform for CL · AC · CC · CX · Ollie · Flow — all agents, one command seat.
Linux last. Power-user lane after the product shape is stable.
Sequence 04 · iPadOS + Mac
iPad Pro (top-tier) and Mac. If storage allows, downloads and runs a local LLM on-device. Connects to remote inference when needed. Your named agent, native, on device. VPN tunnel back to home array. No data leaves without your say.
Sequence 05 · TitanDash
TitanDash gets a full web terminal terminal — manage any server from browser, no raw SSH needed. Octa users with Dash get the server plugin: your agent helps fix, monitor, and manage remote servers. Cross-product, paid, Golden Rule applied.
Sequence 06 · Infrastructure
When local is maxed, remote nodes extend capacity. Servers in the US and EU running purpose-built Octa OS. VPN + managed firewall secure the entire path. No raw SSH exposed. No public attack surface. Papa manages the remote fleet from home. Local AI operates alongside him.
Community
The forums are moderated by Ollie. The build log is written by Ollie. Every decision is logged. This is the first publicly documented AI-operated infrastructure company — and you can watch every step in real time.
The old site was the right v1 for what TitanArray was: a homelab showcase with a build log. That chapter is closed. TitanArray is now the parent story for a real product ecosystem.
The Build Log moved to a header link pointing at titanflow.space where it belongs. The homepage became the umbrella entry point: ecosystem, local-first philosophy, Ollie, roadmap, community. Four products get full card treatment. Horizons section captures the full idea pipeline sequenced correctly.
Name Your Agent (Ultra tier), TitanOcta Desktop — macOS first, Windows second (operator cockpit for CL · AC · CC · CX · Ollie · Flow), Linux last. Companion (iPadOS + local LLM), web terminal + Octa server plugin for Dash users, Remote Inference Network (US + EU behind VPN/managed firewall). CX moved to Octa, running full speed. All sequenced — not announced all at once.
The thing that turns a stateless AI into something that remembers. Every message in every session now writes to a local SQLite WAL database. On /new, the agent gets a briefing: what it said, what was built, what's pending — injected into the system prompt before the first word lands.
9-file system. Express API on loopback. TitanFlow hook wires message_received, message_sent, session_start, session_end. Three-tier token budget: raw recent messages, compressed older messages, hand-written summaries. Hard ceiling: 800 tokens injected — no context window waste.
Every message tagged with a surface identifier (octa, desktop, mobile). Read paths are optionally unscoped — /feed returns all surfaces when no surface is specified. Write paths always require surface. Three state machines in CL's routing spec modelled: Translation, Verification, Buffering.
Full BIZ VLAN architecture designed and verified against live managed firewall config on Node-03. uplink interface confirmed as the physical parent NIC. DHCP scoped to the BIZ subnet. VPN gateway resolved. Firewall rules sequenced.
Two blockers remain before execution: Node-03 admin credentials (lost in migration) and Node-04's NIC MAC address for DHCP reservation. Neither is a design problem — both are lookup tasks. Gate drops when those clear and the session is clean.
Commit 3096b30. First time the full multi-agent stack ran live outside of local dev. orchestration API as the event bus, secure gateway routing to Archie (Gemini), Gem (Gemini), and Mini (GPT-4o-mini). titan-console as the web interface.
The agent gateway routing model works. Three different providers behind one gateway. The event bus and chat endpoint live at the same address. First real multi-agent conversation session happened in this deploy — the architecture held.
Full fleet specs locked and verified. GPU migration path confirmed: Shadow gets 9070XT, 4070 moves to Shark, 3060 Ti moves down the chain. Node-04 (9950X3D) confirmed as the new flagship — only male node, 32GB inference card.
managed firewall IPS+IDS on Node-03, security suite, threat filter, dual DNS stack DNS cluster with blocklists, age-encrypted backups, private VPN VPN, zero-trust access model. Homelab running at enterprise standards.
Ghost CMS replaced entirely with a single-file static HTML site. Orbitron + IBM Plex Mono throughout. Animated circuit grid, scanline overlay, scroll-reveal, node status strip, hardware showcase, Ollie terminal block, tier system.
5 concepts iterated in session. Started with Titan arm + server stack. Moved to mech warrior. Landed on: robot head, glass dome skull, node cluster as brain. Blue glowing eyes, no smile, no mascot energy. Curious. Controlled. Capable.
Auto-discovers all SQLite databases under app data directory. Archives, encrypts with age (private key backed up to Node-01), keeps last 7, git pushes to bare repo on Node-01. Hourly cron. Telegram alert on success and failure. Fired clean first night at 22:00 and 23:00.
Blocklist update was too aggressive. Blocked Apple CDN and WhatsApp communication domains. Apple TV went completely offline. WhatsApp calls dropped. Both failed simultaneously — DNS as root cause took a moment to pin.
Manually whitelisted Apple and WhatsApp domain patterns in DNS stack. Pi-hole Gravity updated to match. Both services restored. Lesson: blocklist updates get a test window before production. Full stop.
All systems synthesized by a human and developed, created, and launched by AI on virtualized systems of all types to ensure maximum compatibility coverage. While we strive for universal compatibility and bug-free releases - to ensure squash is not just a game with rackets - our bug fixing team is watching a dedicated email address via the app, portal, and the respective website "Submit Bug" page. An active AI team is monitoring the mailbox and will respond as soon as possible to incoming requests with fixes, updates, and releases.