Forward Deployed Engineer - Professional Services

World launches World ID suite to help banks tackle deepfake threats. World's press release also pointed to a Deloitte forecast that puts U.S. losses from AI-based fraud at $40 billion by 2027, up from roughly $12.3 billion in 2023. "Enterprises are requesting individuals provide 'Proofs' about themselves to help mitigate fraud and increase trust," said Sandro Herbig, president of Tools for Humanity, the main developer behind World. Design partners are on board, but no bank yet. World said that Bain Capital, VanEck, Pantera Capital, OpenExchange and Outtake have signed on as initial design partners to support and "explore" how World ID can fit into banking and financial services. A World spokesperson told Fortune that some of these firms will keep Orb devices in their offices so that employees who haven't been scanned can sign up. What World didn't announce is a bank. The release named no lender using the product and gave no pricing. Back in April, VanEck was the only finance firm among the Zoom beta testers. AI agents are where World sees the bigger opportunity. The agent tool could end up mattering more than the Zoom badge. Large platforms have mostly treated AI shopping bots as a threat. Amazon sued Perplexity in November 2025 to stop its Comet browser agent from buying things on users' behalf, and Fortune reports that JPMorgan has also started blocking bots outright. Tiago Sada, World's chief product officer, told Fortune that blanket bans will leave those companies behind as agent-driven commerce grows. World's fix works a bit like a power of attorney. A verified user assigns their credentials to one trusted agent, and merchants can then treat that agent as the person. World has competition here. Cloudflare launched its own agent ID tool in August, along with a wallet for agents to use. Regulators are still weighing in on iris scanning. Kenya suspended World's operations in 2023. Spain and Portugal ordered it to stop collecting iris data the following year, and Indonesia froze its permit in May 2025. Banks also tend to move slowly on new identity tech, especially anything involving biometrics and a crypto token. Sada argues the Orb doesn't build a central database and that the code is open source and auditable. He likened the early suspicion to how people first reacted to Apple's Touch ID. The next customer announcement, or a long silence, will say a lot about whether banks agree. Read the full article here

Deno is dead: Cloudflare bought it, 12-month clock. 4 hours ago 50 views 0 Cloudflare bought Deno Land on October 9 and posted two clocks immediately: Deno Deploy shuts down in six months, the Deno runtime gets twelve months of security patches then nothing. Ryan Dahl framed it as joining Cloudflare "to make the Workers programming model mainstream." The honest read is simpler - this is an acquihire for celld, Deno's own open-source implementation of Cloudflare Workers. The runtime was never the point. The two deadlines. If you ship anything on Deno, these are the dates that matter: * Deno Deploy: shuts down approximately April 9, 2027 - six months from announcement. Paying customers get migration support to Cloudflare Workers. * Deno runtime: monthly bug-fix and security releases through approximately October 2027, then Cloudflare ends development. The code stays open source. * JSR package registry: continues - infrastructure moves to Cloudflare, no action required from developers. Six months is not a lot of runway for a production deployment. Treat the Deploy deadline as a hard cutover date, not a soft migration suggestion. What Cloudflare actually bought. The Deno runtime has about 3% server-side JS market share. That is not why a company Cloudflare's size writes an acquisition check. Cloudflare bought celld. Released in August 2026, celld is a single Rust binary that runs the full Cloudflare Workers programming model on infrastructure you own: Workers, Durable Objects, KV, Queues, D1, R2, Workflows, Cron Triggers, and static assets - all driven by your existing wrangler.json. Object storage (S3-compatible, GCS, or Azure Blob) is the only external dependency. That is an enterprise product. Large financial institutions, government contractors, and regulated industries cannot run workloads on Cloudflare's edge network - data residency requirements, compliance mandates. celld removes that blocker. Cloudflare gets those customers without building a private cloud from scratch. Dahl described the progression on the Deno blog: Deno | Deno Deploy | celld was "the path that led to this decision." The runtime was the research phase. celld is the product. Audit your codebase now. Before deciding where to migrate, understand what you actually depend on. Run this in your project root: grep -r "Deno\.". -include="*.ts" -include="*.js" grep -v node_modules What you find falls into two buckets: * Web standard APIs (Request, Response, fetch, crypto, URL, TextEncoder) - portable across every modern runtime. Migration here is trivial. * Deno.* proprietary APIs (Deno.serve, Deno.readTextFile, Deno.openKv, Deno.permissions) - these need runtime-specific replacements. This is the actual work. Three migration paths. Bun - easiest TypeScript path. Bun's Bun.serve is deliberately close to Deno.serve. Both take a fetch-style handler returning a Response. File I/O becomes Bun.file('./config.json').text instead of Deno.readTextFile('./config.json'). Native TypeScript with no compile step. Startup at ~9ms versus Node.js's ~41ms. At 210k req/s on HTTP benchmarks, performance is not a concern. Best for: new TypeScript services, CLI tools, teams that want to stay close to what Deno felt like. Cloudflare Workers - logical for Deploy users. If you are on Deno Deploy, Workers is the named migration path and Cloudflare is offering support for paying customers. The V8 isolate model is identical. Web standard APIs transfer directly. The migration guide from Pinggy covers routing, environment variables, and Durable Objects differences. Best for: existing Deno Deploy apps, stateless HTTP handlers, edge use cases. Node.js - maximum ecosystem coverage. Node.js is not exciting and does not need to be. Node.js 22 supports TypeScript via -experimental-strip-types. The ecosystem is mature, hosting options are universal, and debugging tooling is excellent. You will need to wire up tsconfig and manage the npm dependency tree, but nothing breaks in production in ways that surprise you. Best for: production applications with complex dependency graphs, enterprise reliability requirements. The actual lesson. Dahl himself said it: Deno got "sucked into the gravity well of node compatibility." Each Node.js compatibility shim the team shipped made Deno more like the thing it was supposed to replace - and less compelling as a reason to switch. The runtime that advertised no package.json, first-class TypeScript, and URL-based imports ended up with npm support, a node_modules option, and Deno 2 compatibility flags for legacy code. The community read the announcement clearly. The Hacker News thread hit 1,315 points and 677 comments within a day. One top comment: Deno "was successful for the Node community, but not for Deno the runtime or business." That is a polite way of saying the product did not find its people before the money ran out. celld is interesting and worth watching. Self-hosted Workers with S3 as the only dependency is a legitimately useful primitive. But that story belongs to Cloudflare now, not Deno. I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

Klaviyo: 85% of Klaviyo code is AI-generated. Here's what changes. Published on 10/16/2026 at 11:33 am EDT On September 23, I joined Stephanie Cohen, Cloudflare's chief strategy officer, and Owen Jennings, Block's head of business, on a panel at The Information's AI Agenda Live in San Francisco. [...] Attachments * Original document * Permalink Disclaimer Klaviyo Inc. published this content on October 16, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on October 16, 2026 at 15:32 UTC. (C) Publicnow - 2026