Showcase UI — This flow is a scripted product preview. For live Workers AI (streaming content, social, Q&A, code), use the Swarm agent demos (e.g. Content Agent, Social Agent).

🧩

Telegraph Syndication

Publishes long-form content to Telegraph anonymously — no account required. Every article carries a canonical backlink to your owned blog so you keep SEO authority while maximising reach.

Demo Usage

AI Calls0 / 5

Demos Explored0 / 10

Scripted preview — the Terminal below shows the exact calls the live Cloudflare Worker makes. Telegraph's createPage API requires no account or OAuth token; the Worker calls it directly. URLs shown are representative — run the live Worker to get a real telegra.ph link.

Telegraph Syndication

Anonymous publish → canonical backlink → D1 audit log

v2.1.0

Worker Online

Your Blog Domain

The syndicated article carries a backlink to https://<domain>/blog/<slug>. Enter your blog domain below.

https://

Article to Syndicate

What the Worker Does

1

Pull article from D1

Word count, tags, slug

2

Inject canonical backlink

Links back to your owned blog

3

Append AI disclosure

Compliance — never hidden

4

POST telegra.ph/createPage

No account, no auth token

5

Log URL to D1

Syndication audit trail

worker-log

idle

Select an article and click "Publish to Telegraph" to watch the Worker run…

Article Preview

284 words

Why We Moved Our Database to the Edge

#cloudflare#d1#edge-computing#performance

Moving our database to the edge sounds like an infrastructure nerd flex, but the numbers made the case for us.

Our core product is a content scheduling platform. Every publish action triggers a DB write followed by an immediate read to confirm state. With a centralised Postgres instance in us-east-1, European and APAC users were staring at 380–450 ms round trips just for that confirmation — before any rendering happened.

The switch to Cloudflare D1

D1 is SQLite at the edge, replicated globally. Writes still propagate to a primary, but reads can be served from a regional replica in < 10 ms. For our read-heavy confirmation flow, that's transformative.

Migration was surprisingly straightforward. We exported our schema, ran it through `wrangler d1 execute`, and ported our ORM queries to D1's HTTP API. The whole lift took one sprint.

What actually changed

AI DISCLOSURE (appended by Worker)

This article was generated with AI assistance as part of an automated content pipeline. It has been reviewed for factual accuracy. Originally published on https://yourblog.com/blog/why-we-moved-database-to-the-edge.