if you're building with 🦜langchain or the 🪄ai sdk, there's now a native @CloudflareDev ai search integration for both.
feed it your data, it indexes it, and you get grounded context for your agents w/o building the backend yourself.
👉 https://t.co/SjZUBu8gwa
Novo no https://t.co/lAxValp45d: Locais 🗺️
Já pode explorar milhares de locais - saúde, educação, mobilidade, comércio, serviços, cultura e lazer - e comparar os 308 municípios em valores absolutos, por 10 mil habitantes ou por 100 km².
Veja onde existem creches, escolas, farmácias, supermercados, centros de saúde e lares de idosos. Explore também estações ferroviárias, acessos à autoestrada, postos de combustível e carregadores elétricos.
Qual município oferece mais creches por habitante? Onde há mais carregadores elétricos por área? Que territórios não têm correios, estações ou espaços culturais registados?
Uma nova forma de perceber o que existe, identificar o que falta e levar dados concretos para o debate na sua comunidade.
my new favorite pass time is to add interactive diagrams to the @CloudflareDev AI Search docs.
i’ve always been an extremely visual learner; hoping these diagrams help others as well.
@CloudflareDev AI Search now supports sync jobs via the Wrangler CLI. 🛠️
Trigger and monitor syncs directly from your CI/CD pipeline, so your index refreshes automatically whenever content changes.
Check it out:
My first ship as an intern @Cloudflare:
@CloudflareDev AI Search namespaces are now manageable from Wrangler CLI. Create, list, update, and delete namespaces from the CLI, with --json output for scripts and agents
Novo no https://t.co/uwrohohNG7: a rede de contratos públicos agora permite ver de imediato que entidades recorrem mais ao ajuste direto e quais são as que mais alteram os contratos originais.
Uma forma simples de encontrar padrões que antes estavam dispersos em listas e detalhes contratuais.
Today, Cloudflare Email Service enters public beta with the infrastructure layer to make that easy: send, receive, and process email natively from your agents. https://t.co/lM2rYRqZW2
Time to consider not just human visitors, but to treat agents as first-class citizens. Cloudflare’s network now supports real-time content conversion to Markdown at the source using content negotiation headers.
https://t.co/B7wYH4PtA8
I built a self-hosted Sentry clone that runs entirely on Cloudflare Workers, and I think it showcases one of the most underrated features in the Cloudflare ecosystem: Service Bindings.
Let me explain why this matters.
When you have multiple Cloudflare Workers (an API, a webhook handler, a cron job), they all need common things: error tracking, authentication, rate limiting, metrics. The typical solution? External HTTP calls to third-party services. That means:
- 50-200ms latency per call
- Egress fees
- Your data leaving your infrastructure
- Another vendor to manage
Service bindings let Workers call each other directly inside Cloudflare's network. No HTTP. No internet. Just internal RPC with <5ms latency.
With Workers Sentinel, any Worker in my account can just point Sentry-SDK into the Service binding, and have all errors flow into one centralized dashboard, stored in Durable Objects with SQLite. No external calls. No added latency.
Service bindings aren't just for error tracking. You can centralize:
🔐 Authentication — One Worker that validates tokens for all your services
📊 Metrics — Centralized collection without external observability costs
🚦 Rate Limiting — Shared counters that actually work across Workers
🚩 Feature Flags — Instant propagation, no deployment needed
Think of it as building your own internal microservices mesh, but at the edge, with zero network overhead.
Workers Sentinel uses two Durable Objects:
- AuthState (singleton) — users, sessions, projects
- ProjectState (per-project) — issues, events, stats
Events are fingerprinted and grouped intelligently. The dashboard is a Vue.js app served from the same Worker.
I could say i built this to learn Durable Objects or that I needed error tracking for side projects, but honestly I just need a way to show my wife why I'm sending $200/month to some guy named Claudio who apparently helps me write code.
The whole thing is open source. Deploy it to your Cloudflare account, point your Sentry SDKs at it, and you're done.
But more importantly: take a closer look at service bindings. They're the glue that turns a collection of Workers into an actual platform. Most Cloudflare customers I talk to aren't using them, and they're missing out.
To the Sentry team: I love your work. Genuinely. Sentry is battle-tested, has incredible features, and is what you should use for anything that matters. This project is a toy. A learning exercise. A weekend hack that got slightly out of hand.
Please do not trust your production errors to this dummy clone. If your startup goes down at 3 AM because Workers Sentinel missed an edge case, that's on you. I warned you. Use the real thing.
But if you want to learn about Durable Objects, service bindings, and how error tracking works under the hood? Clone away.
Your Workers shouldn't be islands. Connect them.
If you remember my tweet on experimenting with visualizing @Cloudflare Workflows last week
This is what it looks like when a fabulous designer takes your ugly prototype and makes it 10X better
@TheeAndre Appreciate the wellness check. Rough day. Was heads down fire fighting, talking to customers, and then helping write the post mortem that was just published: https://t.co/uTi23Vd4PO
You heard that right, we are giving your domains on Cloudflare an AI Index. 🤖🔎
Creators now get the tool to make their content discoverable by AI, and AI builders get access to better data. All with fair compensation.
Sign up for private beta today!
https://t.co/jt961wFQG8
We announced Email Routing in 2021. It quickly became one of our most popular features. Today, we are announcing Email Sending, a new capability that allows you to send transactional emails directly from Cloudflare Workers.
https://t.co/VxjP9VmG5p
Cloudflare's defenses have been working overtime. Over the past few weeks, we've autonomously blocked hundreds of hyper-volumetric DDoS attacks, with the largest reaching peaks of 5.1 Bpps and 11.5 Tbps. The 11.5 Tbps attack was a UDP flood that mainly came from Google Cloud. Stay tuned for a full breakdown in our upcoming report.
Wanna yap to your website? 🗣️
Try adding conversational search to your website with AutoRAG and NLWeb, an open-source project by Microsoft. Now in experimental beta. 🌟
https://t.co/NBKVoWArew
Have feedback? Tell us at [email protected]