Colab/Kaggle → Permanent Cloudflare OpenAI API Bridge Kit (Durable Object Relay)
colab-cloudflare-openai-relay-kit.jsonHow This 24-Node System Operates (Without Exposing Source Code)
Signal & Trigger Ingress
Captures incoming webhooks, schedules, or app events from Kaggle Notebooks and normalizes schema payloads.
Validation & Deduplication
Filters malformed payloads, strips duplicate events, and prepares structured context variables before core execution.
Proprietary Orchestration
Executes multi-branch routing, AI/data synthesis, and automatic rate-limit backoff inside the downloadable .json package.
Target Delivery & Telemetry
Dispatches verified outputs to n8n / Cursor with dead-letter error recovery.
Why Standard trycloudflare.com Tunnels Fail in Production
When you expose a free Colab or Kaggle GPU using trycloudflare.com, two things break your automation:
- Every session restart generates a new random URL, forcing you to manually update every n8n node and agent config.
- Calling a
trycloudflare.comtunnel from another Cloudflare Worker or edge proxy fails with Cloudflare Error 1016 / 1033 edge routing blocks.
How the Durable Object Reverse-Tunnel (ollama-relay) Solves Both
Instead of proxying into an ephemeral tunnel, your Colab/Kaggle notebook runs a lightweight WebSocket client that dials outbound over plain HTTPS to /connect on your Cloudflare Durable Object. Your agents, n8n workflows, and Cursor IDE hit your permanent https://relay.yourdomain.com/v1/chat/completions URL—and the Durable Object streams tokens back over the persistent WebSocket with zero edge blocks.