Codeanywhere

Status

Codeanywhere’s hosted service shut down on July 1, 2026. The official June 7 announcement closed new signups immediately, kept existing accounts online through June 30, stopped recurring billing, and warned that remaining workspaces and data would become inaccessible after shutdown.

The Hacker News phrase “went out of business” is directionally correct about product availability but stronger than the available evidence. The official source confirms the service and brand were wound down; it does not state that Codeanywhere, Inc. entered bankruptcy or was legally dissolved.

The marketing and pricing pages remained online when checked, but both displayed a sunset banner. Their signup and purchase language is stale and must not be treated as a current offer.

Summary

Codeanywhere was a hosted browser development environment launched in 2009 as PHPanywhere. Its final form combined a VS Code-style web editor, containerized workspaces, terminal and SSH access, Git-provider connections, collaboration, port forwarding, GPU options, and a Continue-powered AI assistant.

It is no longer a usable alternative for new coding-agent workloads.

Problem

Codeanywhere aimed to let developers work from any browser without installing local tools or owning a powerful computer. Preconfigured remote environments reduced onboarding time and kept project execution away from the user’s device.

How It Worked

• Cloud workspaces: Users created remote container environments with selected processors, memory, storage, and preinstalled language tools.

• Browser IDE: A VS Code-based interface provided editing, extensions, themes, keybindings, terminals, debugging, and previews.

• Full terminal access: Users received command-line access and full sudo privileges inside the environment.

• Repository connections: GitHub, GitLab, and Bitbucket integrations cloned existing projects into a workspace.

• Collaboration: Workspaces, terminals, and application previews could be shared with teammates.

• AI assistance: Continue supplied code completion, chat, codebase questions, and natural-language edits.

Security Boundary

• Remote execution: Project commands ran on Codeanywhere infrastructure rather than the developer’s laptop, limiting direct damage to local files.

• Container boundary: Public material described user environments as containers, not one dedicated VM per workspace. Containers normally share a host kernel, so they offer a different boundary from Clawk or Codespaces’ per-environment VM design.

• High guest privilege: Full sudo access increased flexibility inside the workspace and made the platform’s container and host hardening important.

• Shared access risk: Workspace collaboration, SSH tokens, Git connections, and forwarded ports created deliberate paths into the environment.

• Credential exposure: Any secret or Git credential available inside the terminal could be read by project scripts or a coding agent.

• Historical claims: The site advertised TLS in transit, access controls, backups, SOC 2 Type II, ISO 27001, and GDPR compliance. These claims describe the former service and are no longer operational assurances.

Platforms and Agents

• Client: Web browser plus a documented command-line client for Linux, macOS, and Windows.

• Workspace: Cloud-hosted container environments with many language and framework images.

• External systems: SSH connections could attach the editor to other servers and virtual machines.

• Agents: Standard Linux command-line agents could theoretically run in a workspace if installed. Codeanywhere’s built-in AI experience used Continue rather than presenting a dedicated autonomous-agent sandbox.

• Apple workloads: The HN reply correctly noted that Codeanywhere did not supply hosted macOS development environments for iOS or tvOS builds.

Setup

Setup is no longer possible. Before shutdown, a user could sign up, connect a Git provider, select or define a container, clone a repository, and open it in the browser IDE. Dockerfile and dev-container configuration were listed as supported ways to shape environments.

Existing users were instructed to push all work to a remote Git provider or download it from each DevBox before July 1, including hidden files and environment configuration.

Network and Credentials

• Git providers: The service connected to GitHub, GitLab, Bitbucket, and other remotes for clone and push workflows.

• SSH: Users could access terminals over SSH and share an SSH token with collaborators.

• Port forwarding: Applications could be previewed and shared through forwarded ports within configured policy.

• External connectivity: Remote workspaces needed outbound access for Git, packages, APIs, and model providers. No agent-focused hostname allowlist was identified in the remaining public overview.

• Secrets: Credentials stored in files, environment values, shell history, or Git configuration were within reach of workspace commands.

• Post-shutdown: No credentials should be entrusted to the former service. Users should revoke old Codeanywhere Git authorizations, SSH tokens, API keys, and integrations if they have not already done so.

Pricing

There is no current purchasable pricing. Recurring billing ended with the shutdown.

The still-visible pricing page lists former Free, Basic, Premium, and Enterprise plans, but its purchase controls and amounts are stale. They should be retained only as historical evidence, not used for budgeting or vendor comparison.

Strengths

Historical strengths:

• Browser access: A complete editor and terminal worked from low-powered or borrowed devices.

• Fast onboarding: Prebuilt language environments reduced local setup and team drift.

• Broad tooling: Many languages, frameworks, databases, Git providers, SSH targets, and GPU workspaces were advertised.

• Collaboration: Shared editors, terminals, and previews supported pair work and teaching.

• Long operating history: The product helped establish browser-based development over more than fifteen years.

Limits

• Unavailable: The service is offline and accepts no new users.

• Data removed: Codeanywhere warned that data left on the platform would be inaccessible after July 1, 2026.

• Container isolation: The public design did not claim a dedicated VM for every workspace.

• Not agent-specific: It lacked documented per-agent network filters, credential brokering, disposable sessions, change review, and agent audit policy.

• No macOS workspaces: It did not meet the HN use case for iOS, tvOS, and other Apple platform development.

• Stale website: Marketing, signup, login, and pricing elements remain visible despite the shutdown banner, making surface-level status checks misleading.

Activity and Maturity

Checked 2026-07-14.

• Founded: Began as PHPanywhere in 2009 and later became Codeanywhere.

• Sunset announced: June 7, 2026.

• New signups: Closed at announcement.

• Final service day: June 30, 2026.

• Shutdown: July 1, 2026; workspaces, containers, and remaining platform data became inaccessible.

• Billing: Recurring charges were stopped, with no billing for time after service end.

• Current assessment: Discontinued product. The remaining public site is an archive-like marketing surface, not evidence of an operating cloud IDE.

Best Fit

• Current fit: None. Do not start or retain work on Codeanywhere.

• Migration fit: Former users should confirm repositories contain all work and revoke old integrations and credentials.

• Historical fit: Browser-based teaching, onboarding, temporary remote development, and collaboration from constrained client devices.

Comparison

• Versus GitHub Codespaces: Codespaces remains available and gives each codespace a dedicated VM and network. Codeanywhere used remote containers and is discontinued.

• Versus Clawk: Clawk is a local, agent-focused microVM workflow. Codeanywhere was a general hosted cloud IDE with human collaboration as its center.

• Versus SmolVM: SmolVM is active, open source, agent-focused, and designed around disposable hardware-isolated VMs. Codeanywhere was proprietary hosted infrastructure and cannot now be deployed.

• Versus Bitrise remote environments: The HN participant positioned Bitrise as hosted Linux and macOS VM infrastructure. Codeanywhere did not provide the macOS environments needed for Apple platform development.

Hacker News Context

In comment 48893909, user mrbn100ful named Codeanywhere, GitHub Codespaces, and Claude Code on the web as alternatives to hosted isolated development environments. User dietdrb replied in comment 48894058 that none supplied the needed macOS environments and that “CodeAnywhere went out of business.”

The official record confirms that Codeanywhere had already announced its sunset and was scheduled to go offline July 1, twelve days before the HN discussion. It does not establish the company’s legal dissolution.

Direct Sources

• Codeanywhere sunset announcement
• Codeanywhere home page
• Stale pricing page
• Remaining documentation
• HN alternative comment
• HN shutdown claim
• Clawk discussion

Unknowns

• Corporate status: No authoritative bankruptcy, dissolution, acquisition, or successor-company notice was found.

• Data deletion: The announcement says data became inaccessible, but it does not give a verified deletion schedule or retention policy after shutdown.

• Support duration: The post offered a support contact during the wind-down but did not state how long it would remain monitored.

• Authorization cleanup: It is unclear whether Codeanywhere automatically revoked every Git-provider authorization, SSH token, and external integration.

• Enterprise deployments: The fate of former on-premises or customer-cloud enterprise installations is not addressed in the public sunset post.

• Website retirement: No date is given for removing the stale marketing, login, signup, pricing, or documentation pages.

Sources

• • imported AI research note for Codeanywhere.