Relay, an AI workflow automation startup launched as a potential alternative to Zapier, is shutting down its service while founder and CEO Jacob Bank returns to Google to lead product and developer relations for Chrome.

The company will end access for paying customers on September 14, according to an announcement shared by Bank and reported by TechCrunch. Free customers lost access on August 15. Relay had first disclosed plans to close in July, making the shutdown a completed transition rather than a newly announced restructuring.

Bank’s move gives the closure a direct connection to Google’s expanding plans for AI inside the browser. He said Google Chrome is an opportunity to bring his experience building AI-powered productivity tools to a much larger audience, while also signaling that the Chrome team has plans to help people use AI to complete tasks. Google has not publicly detailed those plans in the evidence available for this report.

Relay’s shutdown closes an automation experiment

Relay was built around workflow automation for business and productivity tasks. The service helped users coordinate repetitive work such as document drafting, copyediting, and project management, according to TechCrunch’s reporting. Its positioning placed it in the same broad market as Zapier, but with AI involved in how tasks were created or executed.

The shutdown means customers must move away from Relay rather than wait for a product transition to another Google service. The available reporting does not identify a successor product, migration program, acquisition, or customer-support arrangement. It also does not establish how many employees or customers Relay had when it closed.

That uncertainty matters for companies using AI automation in operational workflows. A service can be technically useful while still carrying platform and continuity risks, particularly when it handles recurring business processes. Relay’s closure is a reminder that buyers need export options, documented workflows, and contingency plans before making an automation product part of a critical process.

Bank returns to Google with Chrome mandate

Bank previously spent more than six years at Google. He joined the company in 2015 after Google acquired Timeful, a scheduling startup he had helped build. During his earlier tenure, Bank worked on products including Gmail, Google Calendar, and Google Chat before leaving to launch Relay.

According to his LinkedIn update, Bank is returning as Google’s vice president of product for Chrome, with responsibility for the product and developer relations teams. TechCrunch reported that some Relay employees are also joining the Chrome organization, but the available source does not specify how many or which roles they will hold.

Bank described the move as a chance to bring AI productivity experiences to more people without giving up personal creativity or judgment. He also said Chrome is a suitable place to collaborate with agents. Those comments point toward browser-based AI that can help users perform multi-step work across web applications, although they do not confirm a particular feature, launch date, or technical architecture.

What the evidence shows — and what it does not

The confirmed business change is Relay’s service shutdown and Bank’s move to Google’s Chrome team. The closure dates come from the company announcement as reported by TechCrunch, while Bank’s new Google role was identified through his LinkedIn profile and his public comments.

The strongest signals about Google’s broader AI reach are company-reported rather than independently verified in the source material. Google recently said that Gemini had surpassed 1 billion users. That figure refers to Google’s overall Gemini reach and should not be read as evidence that Chrome users are already adopting agent-style automation at the same rate.

Google has already placed Gemini in Chrome as an optional browser assistant, following wider integration across the company’s products and search experience. However, the reporting does not confirm whether Bank’s team will build a new agent, expand Gemini’s browser capabilities, or introduce a separate Chrome workflow product. Google and Relay were contacted for more information, but no additional details are included in the available evidence.

For that reason, the move should be understood as a staffing and product-direction signal, not proof of a Google acquisition of Relay or a launched replacement for the startup’s service.

Why the move matters to AI builders and enterprises

For builders, the story highlights the strategic value of the browser as an execution layer for AI agents. A browser sits close to the work people already perform: reading documents, entering data, communicating with colleagues, and moving information between software tools. A capable agent operating there could reduce the need to connect every application through a separate integration layer.

That opportunity also creates difficult product requirements. Browser agents need clear permission models, reliable task execution, recovery when websites change, and strong controls around sensitive information. An assistant that can draft text is easier to govern than one that can submit forms, send messages, or alter business records. Chrome’s large installed base could make distribution easier, but it would also raise the consequences of errors.

Enterprise buyers should watch whether Google offers administrative controls, audit logs, data-boundary commitments, and support for existing identity and security systems. Those features will matter more than a general promise that AI can get work done. Relay’s shutdown also reinforces the importance of evaluating a vendor’s financial durability and data portability alongside model quality.

For Google, bringing Bank and some Relay staff into Chrome could accelerate experimentation with agent-oriented workflows while adding people who have worked directly on automation products. It may also intensify competition with browser assistants, enterprise automation platforms, and software companies building AI features into their own interfaces.

What to watch next

The clearest follow-up signal will be Google’s promised disclosure about AI in Chrome. Developers and product teams should look for details on whether the company is announcing browser agents, new APIs, deeper Gemini integration, or tools for third-party developers.

Other signals include the responsibilities assigned to former Relay employees, the security and permission model for any Chrome agent, and whether Google supports actions across multiple websites or only offers conversational assistance. Enterprise customers should also watch for policy controls, logging, and deployment options.

On the Relay side, the September 14 cutoff for paying customers is the immediate operational deadline. Former users will need to confirm that important workflows, data, and integrations have been exported or replaced before access ends.

Creati.ai perspective

Relay’s shutdown is not evidence that AI workflow automation has failed. It is evidence that the market is still deciding where automation should live: in standalone platforms such as Relay, inside business software, or at the browser layer where users already perform much of their work.

Bank’s return to Google makes Chrome a more important place to watch, but the commercial case will depend on dependable execution and enterprise controls rather than broad agent language. Until Google provides concrete product details, the move is best treated as a credible signal of direction—and a practical warning about relying on young automation vendors for essential workflows.