Skip to content
where do irun this.

Playcode

HostedAI app builder

AI is moving fast. Build your next business with it.

HomepageDocsPricing

Scanned 15 Oct 2026 · Schema v5 · features v21

From
$25/mo

Freemium workspace subscription plus shared metered credits for AI building, Cloud, email and in-app AI

Free tier
Yes

No card required.

Isolation
Firecracker microVM

shares only the hypervisor

Regions
2

Hetzner — primary application infrastructure · Hetzner — primary application infrastructure

Capabilities
19 / 61

8 partial · 24 fail · 0 not assessed

Agent readiness
11/11 · 10/11

read · drive, pre-login surface

Advertised for

AI generated static sites, full stack websites/apps and internal tools; Cloud backends, SQLite by default (Postgres/Redis available), files, jobs and schedules; mobile apps backed by same project

Built for

Non-technical users, then developers

  • · https://playcode.io/: Turn your idea into a website, app or AI-powered product; our cloud to run it and people to help.
  • · https://playcode.io/about: People have ideas; turning knowledge into software previously meant finding developers and committing money.
  • · https://playcode.io/pricing: Free/Pro/Max plans, shared workspace and credits; integrated build/publish experience.

01 Pricing Freemium workspace subscription plus shared metered credits for AI building, Cloud, email and in-app AI

Tier EntryFreeProMax 400Max 800Max 1600Max 4000TopMax 10000
Price $0$25/month or $250/year$100/month or $1000/year$200/month or $2000/year$400/month or $4000/year$1000/month or $10000/year$2500/month or $25000/year
Includes 3 saved projects; private projects; static publishing with branding; 25 members; 4 MB uploads; eligible trial credits100 credits/month; 3 Cloud apps; 100 GB shared traffic/month; PROD 1 CPU/2 GB; DEV 4 CPU/4 GB; 500 email recipients/billing cycle; custom domains/export; unlimited saved projects400 credits/month; 10 Cloud apps; 1000 GB shared traffic/month; PROD 2 CPU/4 GB; DEV 8 CPU/16 GB; 2000 email recipients/billing cycle; custom domains/export; unlimited saved projects800 credits/month; 10 Cloud apps; 1000 GB shared traffic/month; PROD 2 CPU/4 GB; DEV 8 CPU/16 GB; 2000 email recipients/billing cycle; custom domains/export; unlimited saved projects1600 credits/month; 10 Cloud apps; 1000 GB shared traffic/month; PROD 2 CPU/4 GB; DEV 8 CPU/16 GB; 2000 email recipients/billing cycle; custom domains/export; unlimited saved projects4000 credits/month; 10 Cloud apps; 1000 GB shared traffic/month; PROD 2 CPU/4 GB; DEV 8 CPU/16 GB; 2000 email recipients/billing cycle; custom domains/export; unlimited saved projects10000 credits/month; 10 Cloud apps; 1000 GB shared traffic/month; PROD 2 CPU/4 GB; DEV 8 CPU/16 GB; 2000 email recipients/billing cycle; custom domains/export; unlimited saved projects
Seats25252525252525
Transfer—100 GB1000 GB1000 GB1000 GB1000 GB1000 GB

Workspace plan/month plus credits; 4 subscription credits per USD·Card required: No·playcode.io

Overages: Top-ups $25/100, $50/210, $100/440, $200/960 credits; expire 12 months after latest purchase. Optional auto-recharge minimum $15 at 4 credits/$. Cloud active time/disk/overage traffic consume credits at in-app rates. Email beyond allowance 500 recipients/credit.

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

The desktop landing, pricing and current docs entry share oversized dark sans-serif headings, orange calls to action, rounded outlined panels and recurring illustrated rockets and an expressive orange mascot. Landing and docs place practical input panels over vivid blue-sky launch scenes; pricing uses a quieter warm background and a three-column plan row. The recurring character art, saturated accents and generous headline scale support a Playful interpretation. Coverage is anonymous public entry-page viewports, not the authenticated builder or individual documentation articles.

  • Playful
  • Landing page: captured
  • Pricing: captured
  • Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive
Firecracker microVMshares only the hypervisor
Persistence
Persistent Cloud application databases and files
Snapshots / forks
Computer checkpoints: code, packages, database and uploaded files; restart-based restore

Resources & limits

Storage
Cloud disk up to 200 GB; uploads 4 MB Free / 1 GB paid
Limits & quotas
Free: 3 saved projects, 25 members, static publishing. Pro: 3 Cloud projects, 100 GB/month shared traffic, default PROD 1 CPU/2 GB and DEV 4 CPU/4 GB. Max: 10 Cloud projects, 1000 GB/month traffic, PROD 2 CPU/4 GB and DEV 8 CPU/16 GB. Cloud disk up to 200 GB.
GPU
na

Access

Deploy interface
dashboardclisdkapimcp
SDK languages
JavaScriptTypeScript

Network & secrets

Egress controls
not publicly documented
Secrets
Encrypted, masked per-development/production environment variables
Bring your own cloud
no

Placement & use

Jurisdiction
Primary app infrastructure: Germany/Finland; backups and some processing outside EU
Advertised workloads
AI-generated static sites, full-stack websites/apps and internal tools; Cloud backends, SQLite by default (Postgres/Redis available), files, jobs and schedules; mobile apps backed by same project

04 Capabilities 19 pass · 8 partial · 24 fail · 61 of 61 assessed

  • Supported
  • Partially supported
  • Not supported
  • Not assessed

Compute & storage 1/6

Persistent diskStorage that survives restart/stop (not ephemeral-only).
Not applicable
Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.
Not supported
Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).
Supported
Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.
Not supported
Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.
Partially supported
GPU computeGPU-backed instances available.
Not applicable
Multi-regionCompute placeable in more than one geographic region.
Partially supported
Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).
Not applicable
Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.
Not applicable
Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.
Not applicable
Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.
Not supported

Networking & delivery 5/7

Automatic HTTPSTLS endpoints provisioned automatically per workload.
Supported
Built-in reverse proxyPlatform routes external traffic to workload services.
Supported
Custom domainsBring-your-own domain via CNAME/DNS.
Supported
Public preview URLsShareable per-deploy / per-branch URLs.
Supported
Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.
Not applicable
Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).
Not supported
Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.
Not supported
Email send / receiveSend and/or receive email from the workload.
Supported
Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.
Not applicable

Developer access 4/9

Public APIDocumented programmatic API.
Supported
OpenAPI specMachine-readable OpenAPI / Swagger spec published.
Not supported
CLIOfficial command-line tool.
Supported
SDKOfficial client library/libraries.
Supported
SSH accessDirect SSH into workloads.
Not supported
Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.
Supported
Git deployDeploy from a Git repo / push-to-deploy.
Partially supported
Private container registryHosted private image registry.
Not applicable
E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).
Not supported
HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.
Not supported

AI & agents 4/11

Built-in coding agentShips a first-party AI coding agent in the product.
Supported
Agent skillsInstallable / declarable agent skills or tools.
Partially supported
AI app builderPrompt-to-app / vibe-coding generation surface.
Supported
MCP serverExposes a Model Context Protocol server for agents.
Supported
MCP clientActs as an MCP client / consumes MCP tools.
Not supported
MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).
Not applicable
LLM gatewayRoutes LLM API calls through the platform (multi-provider).
Supported
BYOK for LLMsBring-your-own LLM provider keys.
Not supported
Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.
Not supported
Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).
Partially supported
Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).
Not supported
Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).
Not supported

Data 1/4

First-party databasePlatform-provided managed database.
Supported
Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.
Not supported
Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.
Not supported
Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.
Not supported

Platform & operations 1/5

Scheduled tasksCron / scheduled job primitive.
Supported
Durable workflowsDurable execution / long-running workflow primitive.
Not supported
Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).
Not supported
Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).
Partially supported
Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.
Not applicable
Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).
Partially supported

Organisation & security 3/9

Built-in authPlatform-provided authentication / IAM for workloads.
Partially supported
SSO / SAMLEnterprise single sign-on.
Not supported
Secrets managementFirst-class secrets storage / injection.
Supported
TeamsMulti-user team accounts.
Supported
SharingShare a running workload/resource via link (optionally gated).
Supported
BYOCRuns inside the customer's own cloud account.
Not supported
Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).
Not supported
Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).
Not supported
Self-host / OSS coreOpen-source core that can be self-hosted.
Not supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

  • Whole-project code exportcode-export

    “Export the whole project, tests included, and run it on any VPS.” playcode.io

  • AI-generated images/video/music/voice/presentationsai-asset-generation

    “Generate logo concepts, icons, images, short videos, music, sound effects and spoken narration as you build.” playcode.io

  • Voice-driven buildingvoice-input

    “Write in your own words, or dictate with the microphone button.” playcode.io

  • Integrated domain registration/DNSdomain-registration

    “Bring your domain, or buy one in Playcode.” playcode.io

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

11/11

9 full · 2 partial · 100% of applicable checks

  • llms.txt
    Supported
  • llms-full.txt
    Supported
  • robots.txt AI policy
    Partially supported
  • JSON-LD
    Supported
  • Sitemap
    Supported
  • Meta tags
    Supported
  • Markdown negotiation
    Supported
  • Content efficiency
    Partially supported
  • Docs discoverable
    Supported
  • Machine-readable pricing
    Supported
  • No anti-bot wall
    Supported

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

10/11

6 full · 4 partial · 91% of applicable checks

  • Public API
    Supported
  • OpenAPI spec
    Not supported
  • MCP server
    Supported
  • SDK packages
    Partially supported
  • Auth documented
    Supported
  • Self-serve credentials
    Partially supported
  • Webhooks
    Supported
  • CLI tool
    Supported
  • Error model
    Supported
  • Rate limits documented
    Partially supported
  • Agent config files
    Partially supported

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 3

  • Claude Code Anthropic
    Supported

    External harness through CLI/local MCP or limited hosted MCP; not preinstalled in the workspace.

  • Cursor Anysphere
    Supported

    External harness through CLI/local MCP or limited hosted MCP; not preinstalled in the workspace.

  • Codex CLI OpenAI
    Supported

    External harness through CLI/local MCP or limited hosted MCP; not preinstalled in the workspace.

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 2

  • SOC 2 Type II
    in-progresshosted
  • GDPR
    in-progresshostedEU primary data, but international AI processing and US backups; cookie-consent and explicit analytics opt-in remain roadmap.

Regions 2

  • Hetzner — primary application infrastructureGermany
  • Hetzner — primary application infrastructureFinland

Two disclosed application regions; self-serve selection/failover not documented. Global CDN separate. Privacy/security disclose AWS EU file/email services, US backups and international AI processing.

Legal

Privacy noticeTerms of service

08 Company & presence Facts only, not scored

Company

Headquarters
Europe (specific company jurisdiction undisclosed)
Founded
2016
Team size
Not disclosed
Hiring
Hiring: 4 open positions

Notable people

  • Ruslan Ianberdin — Founder & CEO
  • Anton Isaikin — advisor, Fundraise Up co-founder
  • Yuriy Smirnov — advisor, Fundraise Up co-founder

Activity

Last release
2026-10-14 playcode.io
Last blog post
2026-08-16 playcode.io

Presence 10

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from playcode.io's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema
scan v5
Features registry
v21
Keys tracked today
61
Assessed on this entry
61
Something wrong on this page?

Nearby in the atlas

All AI app builder products →
where do i run this.

An independent spec sheet for places to run code, and the code your agents write. Facts come from each product's public pages; every capability is a count, never a grade.

Verify

Pages change; so do prices. Verify on the vendor's site before you commit; every product page shows when it was read.

Where Do I Run This © 2026counts, not grades · public pages only