Val Town

What Val Town actually is

Val Town is not a VPS, not a traditional PaaS, and not quite a code playground — it sits in its own corner of the serverless-platforms category. The company's own framing is memorable: "If GitHub Gists could run and AWS Lambda were fun." In practice that means you write short TypeScript or JavaScript modules in the browser, each of which becomes a runnable unit (a "val") that can serve HTTP, run on a cron schedule, respond to inbound email, or be imported by other vals. Every val gets a URL, version history, and branch/PR workflows, so the social, GitHub-like layer is built in rather than bolted on.

The platform targets what the founders call "know-code" engineers: people who can write code and want internal tools, automations, and small APIs without touching infrastructure. We think that framing is accurate. If you want a VM with root access, this is the wrong product. If you want to stand up an API endpoint, a nightly report, or a webhook consumer in a few minutes, Val Town is one of the fastest paths available.

Under the hood, vals run in isolated workers with a 4 GiB memory ceiling and a hard 6-hour lifetime per worker, per Val Town's published limits page. Persistence comes from three bundled primitives: a shared SQLite database, blob storage, and the ability to fetch any HTTP endpoint. There is also an email channel — you can send email (yourself on the Free plan, anyone on paid plans) and trigger code from inbound messages. The whole thing is programmable via a documented HTTP API and an official TypeScript SDK, and the project publishes an MCP server and CLI so AI coding tools can drive deployments.

Pricing: what you really pay

The pricing page is short and honest, which we appreciate. Free is $0 and genuinely usable: 100,000 runs per day, unlimited public vals, HTTP endpoints on a val.town subdomain, cron as frequent as 15 minutes, 1 minute of wall-clock time per run, 3 days of log retention, and email to yourself only. For scripts and hobby automation, that ceiling is high — most personal automations never come close to 100,000 runs a day.

Pro is $25 per month billed monthly, or $21 per month billed yearly (two months free). Pro raises the ceiling to 1,000,000 runs per day, 10 minutes of wall-clock time per run, 1-minute cron intervals, 2,000 private vals, 10 custom domains, 10 days of log retention, external email recipients, and $10 per month of credit for "Townie," Val Town's built-in AI coding assistant. Business starts at $167 per month billed yearly ($200 monthly) and adds team accounts, 5,000,000 runs per day, unlimited custom domains, Val Town Access (SSO), Slack Connect support, and $100 per month in Townie credit. Enterprise is custom-priced with SOC 2 and log export.

Two things we like here: the limits are published in one place (a dedicated limits page listing per-plan quotas down to log-line lengths), and nothing is metered per-request with a surprise bill at the end. Two things we don't: private vals are a paid feature, which pushes anyone handling real secrets onto Pro, and the Business plan's per-seat economics are opaque until you talk to sales. There is no hourly billing and no per-run metering — it's flat subscription tiers.

Performance & infrastructure

Here is where we have to be careful, because Val Town publishes far less about its infrastructure than an IaaS vendor does. The company does not sell cores, RAM, or disks per plan; compute is serverless and scaled by the platform. What is public: 4 GiB of worker memory, a 10-second idle timeout, a 15-deep request-triggering-request cap, and the wall-clock limits above. Vals deploy to real URLs (a val.town subdomain on Free, custom domains on Pro and up) served over HTTPS.

What is not public: where the workers physically run, what CPU they get, whether there is an SLA, or any published latency/throughput numbers. We could not find a formal uptime SLA outside the custom Enterprise tier, and the status page history is the only reliability signal available. That means we cannot honestly rate Val Town's raw performance against the VMs and bare-metal hosts we benchmark — see /benchmarks for those. Our expectation, based on the platform's design rather than on measured data, is that cold-start behavior and per-run latency suit small APIs and cron jobs fine, while anything needing sustained CPU should go elsewhere.

On data residency the same gap applies: Val Town does not document EU/US/APAC region selection for compute or storage. If data residency is a compliance requirement for you, this is a question for their sales team before you commit, not something we can confirm from public materials.

Where it falls short

The language story is narrow. Vals are JavaScript and TypeScript only, running on a Deno-style web-standard runtime. Python, Go, and Rust are out. For a lot of automation that's fine; for teams with a polyglot stack it's a real constraint.

The limits bite in specific places. The 80,000-character file size cap means you can't paste a large single-file app into one val; you'll be splitting into modules. The 1-minute execution ceiling on Free rules out anything long-running, and even Pro's 10 minutes is not a batch-processing runtime. Log retention of 3 to 10 days is short for debugging production issues — if you need audit trails, you're exporting logs yourself (a feature that, notably, is Enterprise-only).

There's also a product-maturity question. Val Town is a venture-backed seed-stage company (Accel, founded 2022, Brooklyn-based) with a small team. The platform has moved fast — Projects, Townie AI, MCP integration — but pricing and plan names have shifted more than once, and we'd treat any long-lived production dependency as a bet on a young company. The social, public-by-default model is charming for sharing scripts and a hazard for anything sensitive; the default posture is public code, and privacy is the paid upgrade.

Finally, no SLA, no documented support response times on Free or Pro, and no self-hosted option. If the service has a bad week, your recourse is the status page and a Discord community.

Who should pick this

We'd pick Val Town when the job is small, script-shaped, and needs to live on the internet: personal APIs, scheduled reports, webhook glue, RSS-to-email bots, lightweight internal tools for a small team. The zero-setup path from "idea" to "URL that runs" is the product's real strength, and on the Free plan it costs nothing to try.

We'd skip it for anything needing guaranteed latency, long-running compute, non-JS languages, strict data residency, or contractual uptime guarantees. Production-critical systems with compliance obligations belong on infrastructure with published SLAs — see /category/serverless-platforms for the sturdier end of that market.

For the solo builder or small team who already lives in TypeScript, the Pro plan at $21–25 per month is the sweet spot: private vals, custom domains, and 1M runs a day cover almost every realistic internal-tool workload. The jump to Business is justified the moment you need SSO or shared team workspaces, not before.

Migrating off later is cheap if you keep the code disciplined: vals are ordinary TypeScript functions calling fetch, so the escape hatch is any container or serverless runtime that speaks HTTP. We would keep vals small and single-purpose, hold secrets in the platform's environment variables, and treat Val Town as a fast first home rather than a permanent address. That posture costs nothing today and keeps the exit door open tomorrow, which is exactly what we want from a platform this young.

Key takeaways

• Vals run TypeScript/JavaScript as HTTP endpoints, cron jobs, and email-triggered workers, with SQLite, blobs, and email built in.
• Free plan ($0) allows 100,000 runs/day but public-only code; Pro is $25 monthly or $21/month billed yearly with 1M runs/day and private vals.
• Publishes clear per-plan limits (4 GiB worker memory, 1–10 min run caps) but no infrastructure locations, no SLA outside Enterprise, and no performance benchmarks.
• JavaScript/TypeScript only, 80,000-character file cap, and 3–10 days of log retention are the practical ceilings.
• Founded 2022 in Brooklyn, seed-stage company — best for automations and internal tools, not for compliance-heavy production workloads.
• Our view: the fastest path from script to public URL we've seen, and an honest free tier — just know what you're not getting (regions, SLA, languages) before you build on it.

Sources

• https://www.val.town/pricing
• https://www.val.town/limits
• https://www.val.town/about
• https://docs.val.town/faq
• https://platform.tracxn.com/a/d/company/62c46724930a1f4f45e03411/val%20town