Refact Cloud is shutting down soon. Refact itself is not going away: the project will continue as open source, local-first, BYOK, and community maintained.
Thank you to everyone who built with Refact Cloud, tried the product, shared feedback, reported bugs, contributed code, and trusted Refact inside real engineering workflows. We built Refact to make software development more autonomous, more transparent, and more useful inside the tools developers already use. Seeing people use it to automate real work has meant a lot to us.
The hosted cloud product, however, is being retired. Going forward, Refact will be open-source only. There will be no managed Refact Cloud service, no hosted Refact accounts, no Refact-issued model credits, and no paid cloud subscription layer.
The important difference from many shutdowns is that Refact has already transitioned to a local architecture. The current product is designed to run from your IDE with a local Refact engine and the providers or local runtimes you configure. You do not need a hosted Refact account or managed Refact inference service to keep using it.
We are retiring hosted Refact Cloud services, including:
After the shutdown, these services will no longer be available. We will publish the final shutdown date separately.
Refact’s local-first product continues to work:
Your local configuration and local project data remain under your control. Refact sends requests only to the providers, local runtimes, and integrations you configure.
If you currently rely on Refact Cloud, please prepare for the shutdown:
The latest local architecture is already the recommended path. Once configured, chat, agent workflows, local models, BYOK providers, and integrations can run without Refact Cloud.
Active Refact Cloud subscriptions will be terminated. Invoices paid in the last 30 days before shutdown will be refunded.
There will be no paid hosted service or commercial cloud support after the transition. Support, roadmap discussion, bug reports, and contributions will move to the open-source project through GitHub issues, discussions, and pull requests.
We still believe in Refact’s future as a local coding agent: one that deeply understands your codebase, works with your tools, and lets you choose the model provider or local runtime that fits your workflow.
The next chapter is open source and community maintained. We will focus the project around the local engine, IDE plugins, BYOK providers, local models, and agent integrations that developers can run and inspect themselves.
To everyone who used Refact Cloud and helped shape Refact: thank you. We are grateful for the trust, feedback, and energy you put into the project.
The Refact team