Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The managed version is currently on a waitlist. The public announcement does not specify activation dates for every organization or a standard price; submitting an application is not deployment acceptance.
- The open-source project already offers deployment to your own Cloudflare account, while the repository still describes it as early access. Complete tooling and documentation for workerd on your own servers remain unfinished.
- The new GitHub repository and Google Workspace capabilities can involve commits, pushes or sending email. Check connection permissions, action approval and actual results first.
- The announcement lists exports including .xlsx, CSV, PDF, Markdown and HTML. Word .docx and PowerPoint .pptx exports are still coming soon.
Choose between the managed waitlist and your own Cloudflare account
The official managed-service announcement presents Cloudflare OS as an agent workspace that understands company context and connects organizational systems. This release opens a waitlist for fully managed deployments, after which Cloudflare will contact applicants. Custom domains, Access policies and AI Gateway choices describe the managed offering's direction, rather than proving that any particular account has access.
An open-source path is already available: the official repository README links to deployment in your own Cloudflare account. Organizations configure, operate and maintain that deployment themselves. The managed offering's precise service scope, pricing, regions and activation schedule still require formal confirmation. This article checked public material on October 2, Beijing time; it did not apply to the waitlist, deploy software or authorize external accounts for readers.
What the GitHub and Google Workspace updates mean
The announcement says an existing GitHub repository can now be connected so an agent can read code, fix issues, add features or prepare a pull request, including creating commits and pushing them. Google Workspace capabilities include researching Gmail threads, drafting and sending email, and connecting an entire Drive, selected folders or individual documents. Announcing these capabilities does not mean an organization should grant access to every resource at once.
Start with a test repository or limited dataset. Confirm the accessing identity, resource scope, proposed action and recipient. Review reads, proposed changes and actual submissions separately. Check email content and recipients before sending, and review code diffs and tests before applying changes. Do not make a production mailing campaign or a push to the main branch your first trial.
A simulated Gatekeeper result does not prove an external action finished
The repository README says Gatekeeper handles external-service authorization, limited resource access, action logs and approval for actions with side effects. It can simulate results for some actions requiring approval, allowing the agent to prepare subsequent work before the user approves or rejects them. Acceptance must check final approval and the service's actual result. A simulated success seen by the agent is not evidence that an email was sent or a change was applied.
External services still require individual configuration. The README notes that many Gatekeepers require OAuth client credentials for the corresponding service. An authorized administrator should check current integration documentation and permissions, connecting only the resources needed. The product's capability framework does not replace the team's account, data and change approvals.
Test the required export format before assuming Word or PowerPoint support
Depending on the content created, the announcement lists exports to Microsoft Excel (.xlsx), CSV, PDF, Markdown or HTML. Microsoft Word (.docx) and PowerPoint (.pptx) exports are still described as coming soon. The ability to create documents and slides does not establish that these two file formats are available.
Test the target format with a short document, a simple spreadsheet or a few slides, checking content, formulas, charts and layout. If a critical deliverable requires .docx or .pptx, first confirm the feature and actual export path, or use a format already accepted. Custom tools can define export behavior, which also needs individual testing.
Validate local trials, account deployments and private servers separately
The README's local quick start uses pnpm run-local on Wrangler and workerd, is accessed at localhost:8787, and stores data in the .wrangler subdirectory. The project explicitly describes this as a local trial path, not a production server deployment method. It also labels the current project early access, with work still to complete.
For deployment in your own Cloudflare account, use the README's official deployment entry and check account prerequisites, integration settings and relevant service charges. Complete tooling and documentation for workerd on your own servers are still coming soon. Do not copy the local quick start and call it production-ready. This article does not provide an unverified complete production deployment command sequence or pricing promise.
Keep acceptance records for a team trial
Record the chosen path, repository version, target task, connected resources and necessary permissions. Use limited data to complete a read, a proposed change and a human review, then check the actual external result, exported file and usage. Assign responsibility for deployment maintenance and failures. If a waitlist application is still awaiting contact, do not list it as a delivered team tool.
An inaccessible entry point, an unconfigured integration, an unavailable export and a connection timeout require their own evidence. Only investigate the network separately when there is clear DNS, TLS or connection-timeout evidence. Changing networks cannot accelerate waitlist approval or add permissions to a third-party account.
Sources
Frequently Asked Questions
Is managed Cloudflare OS available to everyone now?
The official offering is a waitlist, without activation dates for every organization or a standard price. Open-source deployment in your own Cloudflare account and the fully managed waitlist are separate paths.
Can pnpm run-local be used as a production deployment?
No. The README presents it for local trials and explicitly says it is unsuitable for running a production server. Deployment to your own Cloudflare account has a separate entry point.
Are Word and PowerPoint exports available?
The announcement labels .docx and .pptx as coming soon. Currently listed formats include .xlsx, CSV, PDF, Markdown and HTML, subject to acceptance for the actual content created.
Does a successful Gatekeeper result mean an email was sent?
Not necessarily. Actions requiring approval may first return simulated results. Check final approval and the external service's real result rather than treating simulation as completion.
Does public source code mean deployment and model calls are free?
No. Organizations still need to check deployment resources, model costs and integration fees. The public announcement does not fully specify managed pricing or activation conditions.