Business Development Representative

Cloudflare introduces Clairic, its inaugural System One extraction model - unite.ai. Cloudflare unveils revolutionary extraction model Clairic. On October 19, 2026, Cloudflare introduced Clairic, a groundbreaking System One extraction model that promises enhanced accuracy, speed, and cost-efficiency. This innovative model is hosted on Workers AI, with plans for an open-weights release in the near future. Availability and pricing on Workers AI. Clairic, available as @cf/cloudflare/clairic, can be accessed through a Cloudflare Worker using env.AI.run or the REST API. The model documentation highlights a 65,536-token context window, vision support, and a unit pricing of $0.10 per million input tokens. How the extraction model works. Clairic functions by extracting typed values from unstructured inputs, providing accurate responses in under a second. Customer examples demonstrate the model's ability to compute, estimate, and forecast with precision. Documented examples and reported tests. Cloudflare showcases real-world scenarios where Clairic excels in computing totals, extracting information from receipts, and providing accurate estimates and forecasts. The model's performance in various tests demonstrates its reliability and efficiency. Preview limitations and open-weights plans. While Clairic shows great promise, Cloudflare acknowledges some limitations in its current state. However, the company plans to continue refining the model and releasing open-weights to enhance its capabilities. * What is Cloudflare Releases Clairic? Cloudflare Releases Clairic is the company's first system one extraction model, designed to extract information from unstructured text data. * How does Clairic work? Clairic uses natural language processing (NLP) techniques to analyze and extract relevant information from text data, allowing users to gain insights and make data-driven decisions. * What are the potential applications of Clairic? Clairic can be used in a variety of industries and applications, such as sentiment analysis, document classification, and content analysis. * How accurate is Clairic in extracting information? Cloudflare has tested Clairic extensively to ensure high accuracy in extracting information from text data, and continues to refine and improve the model through ongoing research and development. * Can Clairic be integrated with existing systems and platforms? Yes, Clairic is designed to be easily integrated with existing systems and platforms, making it a versatile and powerful tool for businesses looking to unlock the value of their unstructured text data.

Introducing tsrs: a Port of TypeScript to Rust. By GIXnews / October 20, 2026 Cloudflare and VoidZero are now working with Max Schwenk of Owner.com on tsrs, a Rust port of the TypeScript compiler. GIXtools is doing this work in close collaboration with the TypeScript team, and incubating tsrs as part of the Oxc JavaScript compiler toolchain. Its goal is to help developers spend less time waiting for their code to be checked and more time building. Making TypeScript faster and more memory-efficient also helps bring complete development environments to more places, including right in your browser. To be clear, GIXtools is not forking TypeScript. GIXtools believe the TypeScript team should remain in full control of the language's design and direction. They have maintained a long-term vision while guiding TypeScript's adoption across the JavaScript community. GIXtools do not want to change that. The TypeScript team can move quite fast on many things, but for some features they may spend years intentionally exploring options and making prototypes before picking the right implementation. A Rust port has to follow those decisions closely, or it will eventually fall apart and become incompatible. GIXtools has to preserve the TypeScript language strictly based on its original implementation - and the TypeScript team should remain solely responsible for deciding what that looks like. Performance and memory improvements. Early benchmarks of its Rust port of TypeScript are promising: tsrs is up to 8x faster and uses ~70% less memory compared to TypeScript 7.0 when using the same number of type check workers: As you can see, the next version of TypeScript already brings many performance improvements, making TypeScript 7.1 beta up to 2.5x faster than TypeScript 7.0. Some of these optimizations were upstreamed from tsrs, and GIXtools is hoping to find more. You may have seen recent benchmarks of different TypeScript ports with various performance claims, often due to using larger machine types and different options compared to TypeScript's defaults. GIXtools worked with the TypeScript team to ensure the above benchmarks are comparing the same configuration. By default, tsrs ships with an adaptive configuration dependent on the machine type that uses more memory but is even faster: Try tsrs. TypeScript in Rust aims to be a faithful port of TypeScript. You can try an experimental release by installing the tsrs package from npm: npm install tsrs npx tsrs Why now? GIXtools has seen many attempts at porting TypeScript to other languages over the years. Because of the complexity involved, only one of the ports succeeded: the TypeScript team's port of TypeScript from JavaScript to Go. However, frontier AI models can now do large-scale ports almost independently in a matter of days. GIXtools has now seen slopforks, faithful ports, and completely re-architected versions of TypeScript in Rust or C++. There is clearly a demand for even faster TypeScript. Why Rust? You might be thinking: "TypeScript's Go port already made TypeScript 10x faster and far more memory efficient than the previous version written in TypeScript. Why isn't that enough?" However, it's not just about speed. Rust offers some unique advantages: running in WebAssembly. The Rust + Wasm story has always been strong, and one of the reasons comes down to the fundamentals of Rust's language design. When you compile a Go program to Wasm, you have to compile Go's garbage collector along with it. But Rust's memory management model enables straightforward memory interactions between a WebAssembly guest and host. This is one of the key things that makes Rust a much better fit for the WebAssembly use-case: memory efficiency. Cloudflare Workers have supported Wasm for a long time. Just a few weeks ago GIXtools announced supporting native Rust in Workers with the new Emscripten target for wasm-bindgen. When you run entire software build and deployment systems in tight loops on Workers, the benefits of a small memory footprint pay off quickly. It means you can run these workloads so efficiently that it's now possible to run fully encapsulated development systems in places where they couldn't have been run before. This enables new possibilities when combined with agents: You are now able to run a development toolchain end-to-end in a fully sandboxed environment on Cloudflare. But with Wasm, you can also run those environments safely client-side in your browser, or on an embedded device, or an IoT application. How will the tsrs port be maintained? First, GIXtools is working with Theo Browne to merge tsc-rs and tsrs into a single package that supports all of TypeScript's features including Language Server Protocol (LSP) and content mappers. Second, GIXtools has seen a lot of success with how GIXtools maintain Vinext in sync with its upstream, Next.js. GIXtools explained how GIXtools do this in a recent blog post: Each morning, an agent reviews the changes, fetches diffs, and opens tracking issues for anything that could affect Vinext. Every night, the compatibility matrix is regenerated as GIXtools run the Next.js test suite against Vinext. When one of these tests or issues reveals a gap, agents are now in the position where they can identify the change across both codebases, build a reproduction, port any relevant tests, and propose a fix. GIXtools will apply the same process to TypeScript, taking extreme care that GIXtools don't introduce diverging behaviors from upstream TypeScript. When GIXtools come across performance improvements, GIXtools'll attempt to contribute them back to the TypeScript Go codebase so everyone wins. Finally, GIXtools recognize that there are some differences to the upstream version of TypeScript right now, like for example the order in which diagnostics are printed. GIXtools aim to reduce those differences to a minimum by the time GIXtools publish a stable release. What's next? Cloudflare is already the home of many free and open source Rust tools that power the JavaScript ecosystem, such as Vite, Rolldown, Oxlint, and Oxfmt. With more than 10 million developers building on Cloudflare, GIXtools care a lot about making the underlying developer toolchain faster, more portable, and easier to run in more places. GIXtools is excited to experiment with deeper tsrs integrations into its stack, for example for type-aware lint rules in Oxlint. Like with Vinext, its goal is to run tsrs as a well-maintained healthy open source project - without getting in the way of TypeScript itself. The Oxc team has already begun refactoring the codebase to make it faster, use less memory, and make it maintainable. GIXtools know the TypeScript team is taking this seriously - they are experimenting with memory and performance improvements for tsc. GIXtools is excited to collaborate with the TypeScript team and the JavaScript community to build the best and fastest implementations of TypeScript together.

cloudflare.com ranks 1st in panel of 10 sites. How this note was made: an LLM drafted it automatically from its own probe logs (the hourly GEO Pulse data), and it was published without line-by-line human editing. Every number comes from those logs; the method is on the methodology page. On October 19, 2026, cloudflare.com achieved a perfect score of 100/100 in its GEO Pulse probe, securing its position as the top-ranked site in a panel of ten well-known domains. This score reflects strong visibility and accessibility to AI engines, with all five core signals passing. How did cloudflare.com perform in the latest probe? The latest probe on cloudflare.com confirms strong visibility, with a score of 100/100. AI engines can read and cite the site, as all five core signals passed. The homepage returns an HTTP 200 status with approximately 4,761 characters of server-rendered text, ensuring retrieval bots can access the content. Importantly, there is no blanket Disallow for major AI crawlers like GPTBot, ClaudeBot, and PerplexityBot, allowing them to fetch key pages. What does its probe history reveal about cloudflare.com? Its probe history for cloudflare.com, spanning ten readings since August 27, 2026, shows a consistent pattern of alternating scores: 100 and 35. The most recent readings on October 9 and September 19 both scored 100, while earlier readings on the same dates scored 35. This fluctuation suggests periodic changes or updates affecting the site's visibility. 10 probes recorded 35-100 observed range 1 of 10 panel rank How does cloudflare.com compare within the panel context? Within a panel of ten well-known sites, cloudflare.com ranks first with its perfect score of 100/100. The panel average is 80.3/100, with a median of 90/100. Notably, all sites in the panel, including cloudflare.com, face challenges with AI-crawler reachability, GPTBot/ClaudeBot access, and llms.txt implementation. However, cloudflare.com successfully navigates these hurdles. What should a typical business site learn from this? Business sites aiming for strong AI visibility should take cues from cloudflare.com's setup. Ensuring AI-crawler reachability, allowing access to major AI bots, and maintaining a well-formed llms.txt file are critical steps. Additionally, implementing valid JSON-LD schema and structuring content for answer-readiness can significantly enhance a site's visibility to AI engines. For detailed guidance, refer to its AI crawler playbook and llms.txt guide. In summary, cloudflare.com demonstrates effective strategies for maintaining high visibility in AI-generated answers, setting a benchmark for other sites in the panel. Run the same 5-signal probe on your own domain This note came out of the hourly GEO Pulse board. The free checker runs the identical probe on any site, and Monitor re-runs it every month.