cloudflare·Jan 16, 2026·3 min readCurated summary

Astro is joining Cloudflare

Astro Technology Company is joining Cloudflare, with the Astro team continuing to develop the framework as Cloudflare employees. Astro will remain MIT-licensed, open source, portable across platforms, and governed through a public roadmap and open contributions. The partnership aims to strengthen Astro’s role as a fast, accessible framework for content-driven websites, with Astro 6 introducing major development and runtime improvements. ## What the Cloudflare Acquisition Means - Astro remains: - Open source and MIT-licensed - Open to community contributions - Supported by a public roadmap and open governance - Deployable across any cloud or hosting platform - Astro’s full-time employees are joining Cloudflare and will continue working on the framework. - Cloudflare will support the Astro Ecosystem Fund alongside partners such as Webflow, Netlify, Wix, Sentry, and Stainless. - The project’s commitment to portability and platform independence will not change. ## Why Developers Choose Astro Astro has focused on content-driven websites rather than attempting to serve every type of application equally. - **Content-driven:** Built to showcase websites’ content. - **Server-first:** Renders HTML on the server for better performance. - **Fast by default:** Designed to make slow websites difficult to build. - **Easy to use:** Accessible without deep JavaScript tooling expertise. - **Developer-focused:** Provides tools and resources intended to support successful development. Astro’s Islands Architecture supports this approach: - Most pages are delivered as fast, static HTML. - Interactive sections can be rendered as client-side “islands.” - Developers can use multiple UI frameworks on the same page, including React, Vue, Svelte, and Solid. ## Shared Vision for Web Development Cloudflare and Astro share a goal of making the web faster and easier to build on. - Astro was created in 2021 to simplify the increasingly difficult process of building fast websites. - Its simple, structured foundation also helps coding agents and AI-assisted development produce better results. - Platforms including Webflow Cloud, Wix Vibe, and Stainless use Astro to help their customers create and publish websites. - These platforms run on or integrate with Cloudflare infrastructure while using Astro as their content and application foundation. ## Astro 6 Improvements Astro 6 is entering beta, with general availability expected soon. - A redesigned development server is built on Vite’s Environments API. - With the Cloudflare Vite plugin, local development can run in `workerd`, the Cloudflare Workers runtime. - Developers can locally use production-like APIs such as: - Durable Objects - D1 - KV - Agents - The Vite Environments API is not limited to Cloudflare; other JavaScript runtimes can provide similar integrations. - Live Content Collections are now stable, allowing content to update without rebuilding the site while retaining validation and caching. - Additional features include first-class Content Security Policy support, simpler APIs, and Zod 4 support. Cloudflare’s investment is intended to give Astro greater long-term support without changing its open, portable character. Developers can try the Astro 6 beta with `npm create astro@latest -- --ref next` or upgrade an existing project using `npx @astrojs/upgrade beta`.

Read original(opens in new tab)

CloudflareCloudflare WorkersAstroVite+4

meta·Nov 20, 2025Original article

Key Transparency Comes to Messenger (opens in new tab)

Messenger has enhanced the security of its end-to-end encrypted chats by launching key transparency, a system that provides an automated, verifiable record of public encryption keys. By moving beyond manual key comparisons, this feature ensures that users can verify their contacts' identities without technical friction, even when those contacts use multiple devices. This implementation allows Messenger to provide a higher level of assurance that no third party, including Meta, has tampered with or swapped the keys used to secure a conversation. ## The Role of Key Transparency in Encrypted Messaging * Provides a verifiable and auditable record of public keys, ensuring that messages are always encrypted with the correct keys for the intended recipient. * Prevents "man-in-the-middle" attacks by a compromised server by making any unauthorized key changes visible to the system. * Simplifies the user experience by automating the verification process, which previously required users to manually compare long strings of characters across every device their contact owned. ## Architecture and Third-Party Auditing * Built upon the open-source Auditable Key Directory (AKD) library, which was previously used to implement similar security properties for WhatsApp. * Partners with Cloudflare to act as a third-party auditor, maintaining a public Key Transparency Dashboard that allows anyone to verify the integrity of the directory. * Leverages an "epoch" system where the directory is updated and published frequently to ensure that the global log of keys remains current and immutable. ## Scaling for Global Messenger Traffic * Manages a massive database that has already grown to billions of entries, reflecting the high volume of users and the fact that Messenger indexes keys for every individual device a user logs into. * Operates at a high frequency, publishing a new epoch approximately every two minutes, with each update containing hundreds of thousands of new key entries. * Optimized the algorithmic efficiency of the AKD library to ensure that cryptographic proof sizes remain small and manageable, even as the number of updates for a single key grows over time. ## Infrastructure Resilience and Recovery * Improved the system's ability to handle temporary outages and long delays in key sequencing, drawing on two years of operational data from the WhatsApp implementation. * Replaced older proof methods that grew linearly with the height of the transparency tree with more efficient operations to maintain high availability and real-time verification speeds. * Established a robust recovery process to ensure that the transparency log remains consistent even after infrastructure disruptions. By automating the verification of encryption keys through a transparent, audited directory, Messenger has made sophisticated cryptographic security accessible to billions of users. This rollout represents a significant shift in how trust is managed in digital communications, replacing manual user checks with a seamless, background-level guarantee of privacy.

CloudflareSecurityEnd To End EncryptionCryptography+2

figma·Jul 21, 2019·2 min readCurated summary

Behind the Plugins: Sam Mason de Caires, UX Engineer at Cloudflare | Figma Blog

Figma’s early plugin beta highlighted how community-built tools could expand the possibilities of design software. Sam Mason de Caires, a UX Engineer at Cloudflare, sees plugins as a way to automate repetitive work and give designers more time for meaningful creative decisions. He also anticipates a future where generative design tools create many variations from data, with designers refining the best results. ## Sam’s Background and Motivation - Sam became a developer because he enjoys building things from scratch and seeing people use them. - His interest in design overlaps with his development experience, allowing him to contribute to design projects at Cloudflare. - He believes developers can support the design community by creating tools that improve speed and confidence. ## Plugins Sam Is Building - Sam had already created four Figma community plugins. - His projects include: - Translation tools - Data replacement - Theme UI generation - Graph creation - Color references designed to support color-blind users - He is particularly interested in using Figma’s API to automate tasks normally completed manually. ## The Role of Automation in Design - Figma’s plugin API gives creators access to the underlying tool and enables custom workflows. - Automating tedious tasks allows designers to focus on higher-value parts of the process. - Sam views plugins as a bridge between development and design, helping users work more efficiently without leaving their design environment. ## The Future of Design Tools - Sam expects major advances in generative design over the next five years. - Instead of designing every possible state individually, designers may provide data describing the desired output. - Design tools could then generate multiple variations, leaving designers to select and refine the strongest elements. - He recommends Adam Morse’s writing on “Chaos Design” for deeper thinking about the evolution of design tools. ## Contribution to the Design Community - Sam plans to continue creating tools and processes that help designers work faster and with greater confidence. - He is inspired by Stripe, praising both its visual quality and its success in making payment processing feel like a desirable product. - He also admires Stripe’s efforts to support broader communities through initiatives such as Stripe Press. Sam’s plugins were scheduled to become publicly available in Figma on August 1, 2019, reflecting Figma’s broader effort to build its plugin ecosystem around community innovation.

Read original(opens in new tab)

CloudflareFigmaFigma PluginsPlugin Api+2