Val Town

Used when a val needs simple key/value persistence — JSON documents, cached responses, uploaded files, or binary assets.

@val-town10

Used when a val needs to ship JavaScript that runs in the browser — React apps, vanilla DOM scripts, canvas/games,...

@val-town10

Used when the user wants to persist a preference, skill, or knowledge.

@val-town10

Used when building a val that runs on a schedule — periodic jobs, recurring tasks, polling, cron jobs, monitoring,...

@val-town10

Used when a val sends email, receives email, or is triggered by an incoming email.

@val-town10

Used when building an HTTP val — a web endpoint, API route, webhook receiver, or any val that responds to HTTP requests.

@val-town10

Used when a val needs to require login with a Val Town account — gating routes behind authentication, identifying the...

@val-town10

Used when building any val with a user interface — dashboards, web apps, landing pages, forms, admin tools, anything...

@val-town10

Used when a val's HTTP endpoints should not be open to the whole internet — limiting an app to a team, understanding...

@val-town10

Used when a val needs to store structured or relational data.

@val-town10

Used when a val talks to an external service — Slack, Discord, Telegram, Stripe, GitHub, Gmail, Google Sheets,...

@val-town10