Prized

HostedAI app builder

Build internal tools with AI. Safely.

Homepage Pricing

Scanned 7 Aug 2026 · Schema v5 · features v17

From: $100/mo
Flat per-workspace subscription with a monthly BUILD allowance, plus optional opt-in pay-as-you-go beyond it. Seats are unlimited and never billed.
Free tier: Yes
No card required.
Isolation: Not disclosed
the public docs do not say
Regions: —
No region, data-residency or jurisdiction information is published anywhere — not on the homepage, pricing page, privacy notice or ToS, and there is no security/trust page (it redirects to sign-in). The marketing site and console are served from Vercel's edge (`x-vercel-id: fra1::iad1::...`), but that describes PRIZED'S OWN site, not where customer tools or connector traffic are processed, and must not be read as a region disclosure. Notable gap given the product connects to production systems of record for finance and support teams.
Capabilities: 10 / 54
4 partial · 28 fail · 7 not assessed
Agent readiness: 5/11 · 0/11
read · drive, pre-login surface

Advertised for

Internal line of business tools: record lookups, approval queues, BI style dashboards, inventory/ops trackers.

Built for

Non-technical users, then technical

· Hero targets job functions, not engineers: 'For the ops, support, and finance teams who run the work.'
· YC description: 'Prized lets non-engineers build, deploy, and share secure internal tools with AI, no engineering required.'
· Blog: 'the people who do the work should build the software that runs it, without writing a line of code.'

01 Pricing Flat per-workspace subscription with a monthly BUILD allowance, plus optional opt-in pay-as-you-go beyond it. Seats are unlimited and never billed.

Tier	EntryFree	Teams	TopEnterprise
Price	$0	$100/mo per workspace	Custom
Includes	2 tools a month, no card required; 30 agent messages per tool; unlimited seats; live preview sandboxes; standard connectors (Postgres, Snowflake, Slack, and more).	Everything in Free; 500 tools a month; unlimited agent messages; custom domain for every tool; optional pay-as-you-go extra usage; SSO/SAML; audit log; RBAC and role-scoped connectors; priority support.	Everything in Teams; unlimited usage (fair use); dedicated support and onboarding; invoice billing and custom terms.

tool builds / edit sessions per month, per workspace (a fork costs a fraction of a full build; running a deployed tool is free)·Card required: No·prized.dev

Overages: Opt-in pay-as-you-go on paid plans once the monthly build allowance is exhausted; the per-unit rate is disclosed only in the logged-in billing settings, never on the public page. Without opt-in, builds pause and deployed tools keep running.

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

Isolation & lifecycle

Isolation primitive

Not disclosedthe public docs do not say

Persistence

Deployed tools are durable and stay live independent of the build allowance; tool DATA is not stored by Prized — tools read the customer's own connected systems of record.

Snapshots / forks

Tool-level forking + published versions — not compute-instance snapshots.

Resources & limits

Storage

No first-party data store offered to tools. Tools read/write the customer's connected systems (Postgres, Snowflake, MongoDB, Salesforce, Stripe, Zendesk, Slack, Notion, Google Sheets, HubSpot, Intercom, Asana, Trello, Figma, Dropbox, Microsoft Teams, Zapier).

Limits & quotas

Free: 2 tools/month + 30 agent messages per tool. Teams: 500 tools/month + unlimited agent messages. Enterprise: unlimited (fair use). All plans: unlimited seats. Running a deployed tool is never metered.

GPU

Access

Deploy interface

dashboard

SDK languages

Not documented

Network & secrets

Egress controls

Outbound calls from a generated tool are proxied through a platform-controlled layer; each tool's reach is limited to admin-approved connectors and an explicit grant list.

Secrets

Workspace-scoped connector credentials, approved once by an admin and reused by every tool — no general-purpose secret store documented.

Bring your own cloud

Placement & use

Jurisdiction

Not documented

Advertised workloads

Internal line-of-business tools: record lookups, approval queues, BI-style dashboards, inventory/ops trackers.

03 Capabilities 10 pass · 4 partial · 28 fail · 54 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 0/4

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).

Partially 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 assessed

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.

Not supported

GPU computeGPU-backed instances available.

Not applicable

Multi-regionCompute placeable in more than one geographic region.

Not 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 assessed

Networking & delivery 4/7

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Partially 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).

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.

Not 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 0/6

Public APIDocumented programmatic API.

Not supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Not supported

CLIOfficial command-line tool.

Not supported

SDKOfficial client library/libraries.

Not supported

SSH accessDirect SSH into workloads.

Not applicable

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not applicable

Git deployDeploy from a Git repo / push-to-deploy.

Not 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 assessed

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 2/9

Built-in coding agentShips a first-party AI coding agent in the product.

Supported

Agent skillsInstallable / declarable agent skills or tools.

Not supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Supported

MCP serverExposes a Model Context Protocol server for agents.

Not 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).

Not 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).

Not 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 assessed

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 assessed

Data 0/4

First-party databasePlatform-provided managed database.

Not 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 0/5

Scheduled tasksCron / scheduled job primitive.

Not 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).

Not supported

Organisation & security 4/7

Built-in authPlatform-provided authentication / IAM for workloads.

Supported

SSO / SAMLEnterprise single sign-on.

Supported

Secrets managementFirst-class secrets storage / injection.

Partially 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 assessed

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 assessed

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.

Admin-approved, workspace-scoped data connector cataloguegoverned-data-connectors
“Company data, pre-connected. Admins approve each connector once and scope what it can see. Every tool you build reuses it.” prized.dev
Per-tool data grant list (row/table-scoped access identity per generated app)per-workload-data-grants
“Each tool runs with its own role and grant list, never blanket database access.” prized.dev
Workspace access audit log over tool runs and data touchesaccess-audit-log
“The workspace audit log records who ran each tool, what it touched, and when.” prized.dev

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

Can an agent read it?

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

5/11

3 full · 4 partial · 45% of applicable checks

llms.txt
Not supported
“GET /llms.txt -> HTTP 200 text/html, the Next.js sign-in shell (76.9 KB), not a text file. No docs subdomain exists to host an alternate copy (rubric v3 allows docs.<domain>/llms.txt — there is no docs host).”
llms-full.txt
Not supported
“GET /llms-full.txt -> HTTP 200 text/html, same SPA shell (76899 bytes).”
robots.txt AI policy
Partially supported
“robots.txt exists: 'User-Agent: * / Allow: / / Disallow: /api/ /admin /sign-in /invite /oauth' + a Sitemap: pointer. Silent on AI user-agents — no GPTBot/ClaudeBot/PerplexityBot/Google-Extended directives either way = default-allow.”
JSON-LD
Partially supported
“Homepage ships valid schema.org JSON-LD with an @graph of exactly Organization + WebSite (name, url, logo, description, publisher). No SoftwareApplication/Product/Offer node — the rubric's 'minimal' band.”
Sitemap
Partially supported
“/sitemap.xml is a real XML urlset with 4 URLs (/, /blog/backed-by-y-combinator, /legal/privacy, /legal/terms) and lastmod/changefreq/priority. Valid but <5 URLs = trivial.”
Meta tags
Supported
“Complete and descriptive: <title>'Prized - Build internal tools with AI. Safely'</title>, a 226-char meta description, canonical, application-name, theme-color (light+dark), and a full OG set (og:title, og:description, og:site_name, og:image + og:image:type).”
Markdown negotiation
Not supported
“Re-requesting / with 'Accept: text/markdown' returns text/html (identical 124674 bytes). /index.md returns the SPA shell, not markdown.”
Content efficiency
Partially supported
“Homepage readable text 3289 chars / 124641 bytes HTML = 2.64% — inside the 1-5% band. Next.js server-rendered, but the markup is animation-heavy and the RSC payload is duplicated inline.”
Docs discoverable
Not supported
“No docs link in the header, nav or footer (footer is: Guardrails, Audit, Sign in, Schedule a call, Privacy, Terms). /docs 307s to app.prized.dev/sign-in — documentation is entirely login-gated, so an unauthenticated agent can find none of it.”
Machine-readable pricing
Supported
“/pricing is a real page with three structured, parseable tiers (Free $0 / Teams $100 per mo per workspace / Enterprise Custom), explicit per-tier feature bullets, and 6 FAQ entries defining the usage model. No 'contact us'-only wall.”
No anti-bot wall
Supported
“No challenge on any public path — plain curl fetched /, /pricing, /robots.txt, /sitemap.xml, /legal/*, /blog/* at HTTP 200 with no Turnstile/Cloudflare interstitial. Auth surfaces are gated by Google OAuth, which the rubric explicitly does not penalise.”

Can an agent drive it?

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

0/11

0 full · 0 partial · 0% of applicable checks

Public API
Not supported
“No public API mentioned on any reachable page. robots.txt disallows /api/ (the console's own internal endpoint). Docs are login-gated, so this is a FLOOR — see meta.scan_issues.”
OpenAPI spec
Not supported
“/openapi.json and /api/openapi.json both return the Next.js sign-in shell (HTTP 200, text/html); no spec referenced anywhere.”
MCP server
Not supported
“/.well-known/mcp returns the SPA shell. No mcp.prized.dev endpoint, no npm/pip MCP package, and the phrase 'Model Context Protocol' appears nowhere on the public surface (rubric v3 guard applied: no bare-substring false positive).”
SDK packages
Not supported
“No official or community SDK/client library referenced; no npm or PyPI package named.”
Auth documented
Not supported
“No API-auth, OAuth-for-third-parties, token or scoped-key documentation is publicly reachable. The only documented auth is human sign-in: 'Continue with Google' (ToS: 'When you sign in with Google we match your account to a workspace by email domain or invitation').”
Self-serve credentials
Not supported
“There is no credential for a machine to obtain at all — no API keys, tokens or service accounts exist on the public surface. Human signup IS self-serve and low-friction (Google OAuth, no card, no sales call), but it yields a browser session, not a programmatic credential, so this scores none rather than half.”
Webhooks
Not supported
“No webhooks, event subscriptions or callbacks mentioned (nor signing docs).”
CLI tool
Not supported
“No official or community CLI. The product's entire interaction model is a browser chat UI.”
Error model
Not supported
“No API documentation exists publicly, therefore no documented JSON error model. Scored fail not na: an internal-tools platform plausibly could expose an API (Retool does).”
Rate limits documented
Not supported
“No API rate limits or response headers documented. The only published quotas are commercial build allowances on /pricing (2 vs 500 tools/month), which are not API rate limits.”
Agent config files
Not supported
“/agents.md and /.well-known/agent both return the SPA shell; no skills listing, no agent-facing configuration surface of any kind.”

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

Advertised integrations 0

The public surface names no coding harness as supported or documented-to-run-here.

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.

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

Certifications held 0

No attestations found on the public surface. Empty means nothing is advertised, after checking, not that nothing was checked.

Regions —

Regions are not disclosed on the public surface.

No region, data-residency or jurisdiction information is published anywhere — not on the homepage, pricing page, privacy notice or ToS, and there is no security/trust page (it redirects to sign-in). The marketing site and console are served from Vercel's edge (`x-vercel-id: fra1::iad1::...`), but that describes PRIZED'S OWN site, not where customer tools or connector traffic are processed, and must not be read as a region disclosure. Notable gap given the product connects to production systems of record for finance and support teams.

Legal

Privacy notice Terms of service

07 Company & presence Facts only, not scored

Company

Headquarters: San Francisco, CA, USA
Founded: —
Team size: 2 (both founders; no other team members disclosed)
Hiring: Unknown

Notable people

Hudson Griffith — co-founder. Founding engineer at Gander (YC F24, acquired by Archer Aviation, NYSE: ACHR), then full-stack at Suno.
Marinos Eliades — co-founder. Stanford CS + Mechanical Engineering; engineer at Gander (same team as Hudson); previously co-founded Loophole (AI employee-onboarding); served in the National Guard of Cyprus.

Activity

Last release: —
Last blog post: 2026-06-30 prized.dev

Presence 4

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

08 Sources & method How this entry was produced

Public surface only

Everything here was read from prized.dev's unauthenticated pages, docs, pricing and repository on 7 Aug 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v17). “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: v17
Keys tracked today: 61
Assessed on this entry: 54

Something wrong on this page?

Nearby in the atlas

All AI app builder products →