Val Town Shutting Down: Export Your Vals and Move Them

Val Town goes read-only on December 10 and shuts down on January 10, 2027. Download your vals, env vars, SQLite and blobs, adapt the Deno code to Node.js, deploy it and replace your val.run URLs.

The RoamerHost Team 8 min read
Ready to start? Vibe Coding Hosting, set up in 60 seconds Put your vibe-coded web app online. From avg. NT$299/mo (billed yearly). Subscribe to Vibe Coding Hosting
On this page

Val Town announced on November 10, 2026 that it is winding down. Code becomes read-only on December 10, and every remaining service shuts down on January 10, 2027. If you have HTTP endpoints, cron jobs or data there, they need to move before then. The order that causes the least trouble: download your code, environment variables, SQLite data and blobs; adapt the code to run on Node.js; deploy it on a new host; then replace your old val.run URLs.

This guide uses RoamerHost's Vibe Coding Hosting as the destination. RoamerHost is run by a team in Taiwan, bills in Taiwan dollars with proper invoices, and lets your own AI coding tool deploy over MCP. Val Town runs your code on Deno and we run Node.js, so there is a small rewrite involved; the sections below show exactly where.

Val Town's dates and export options come from its November 10 announcement and its official documentation, checked on November 20, 2026. If Val Town updates them, its official pages take precedence.

What Val Town announced

The post "Val Town is winding down" sets out the timeline. New sign-ups and plan upgrades ended on November 10. Read-only mode starts on December 10, though SQLite and blob storage are not part of that step. All other services shut down on January 10, 2027, and Val Town's code will be released as open source on February 1, 2027. Billing was paused on November 10, existing subscriptions keep running for free until the end, and people who prepaid for a year get a partial refund.

The date that matters most is December 10. After that you can no longer edit your vals, so fixing things while you migrate gets much harder. Your data stays writable until January, but moving it together with the code keeps the two in sync.

Step one: download your code and data

Val Town's documentation lists several export options. You can download a whole val as a ZIP file or grab files one at a time, and export your environment variables as a .env file. Each val's admin panel can dump its SQLite database as SQL or export a single table as CSV, and the Blob Storage menu lets you list and download blobs.

The .env file holds API keys and passwords, so keep it on your own machine and out of chats and Git. While you're at it, make a list: which vals are HTTP, cron or email triggers, which environment variables, databases and blobs each one uses, and which outside services call its val.run URL, such as payment notifications, LINE, forms or other apps.

Step two: get the Deno code running on Node.js

Vals are TypeScript running on Deno. An HTTP val exports a function that takes a Request and returns a Response. That pattern is a web standard, but Node.js won't give it a URL by itself: you need a small server that wraps it and listens on 0.0.0.0 and the PORT environment variable. Packages imported by URL or with the npm: prefix become regular dependencies in package.json, and Val Town's own standard library for email, blobs and SQLite needs a replacement.

This is a good job for the AI coding tool you already use. Hand it the ZIP files and ask it to combine the vals into one Node.js project, with each HTTP val as its own route, listening on PORT. Val Town's announcement makes the same point: AI models handle this kind of migration well. Run it once on your own computer and check that every route responds.

Step three: map crons, data and email

Vibe Coding Hosting has no cron vals. Instead, you turn each job into a URL and set up a schedule on the project page or through your AI, and the platform calls that URL on time. Schedules use Taipei time, run at most every 5 minutes, get up to 120 seconds per run, and each project can have up to 5. Val Town crons run in UTC, so add 8 hours when you convert them. Since anyone can reach that URL, add a secret string to it and have your code check it before doing any work.

For data, the platform supports SQLite, PostgreSQL 16 and MariaDB 11.4. To change as little code as possible, keep SQLite and store the database file in /data, which survives redeploys. If you'd rather use PostgreSQL or MariaDB, import the SQL dump: up to 95MB through your AI over MCP, or 32MB from the dashboard. SQLite's SQL dialect differs from both, so ask your AI to convert the dump first. Blob files go into /data as well.

Outgoing email has to go through an email provider's HTTPS API, because apps can't connect to SMTP directly. Vals triggered by incoming email have no equivalent here, so plan how you'll handle those before you move.

Step four: deploy

Once your Vibe Coding Hosting project is open, there are three ways to get code onto it. Create an MCP token on the project page, give it to your AI coding tool, and ask it to deploy and fix whatever the logs report. If the code is on GitHub, connect the repo and every push to the chosen branch deploys automatically. Or zip the project and upload it from the dashboard. A package.json tells the platform to build with Node.js 22 or 24. A new version only goes live after it passes a health check; if it fails, the old version keeps serving and you're told why.

Each plan holds one site. Many Val Town users have several vals, each with its own URL. Combine them into one project with separate routes and a single plan covers them. If you really need two independent sites, that's two plans.

Step five: replace your val.run URLs

Test every route on the default yourname.roamerhost.com address first. Then update everything outside that still points at val.run: payment and LINE webhooks, OAuth callback URLs for Google or GitHub sign-in, form actions, and API URLs used by other apps. To use your own domain, add it on the project page; once DNS is set, SSL is issued and renewed automatically.

Run old and new side by side for a few days. When the schedules fire on time and the webhooks arrive, switch off the vals on Val Town.

What Vibe Coding Hosting doesn't run

It runs websites and web apps that serve HTTP at a URL. It doesn't support long-running background workers, always-connected bots such as Discord bots, your own Redis or MongoDB, Dockerfiles, or languages like Go and Rust. Most of what people build on Val Town, such as HTTP endpoints, webhook receivers, jobs that can be triggered on a schedule through a URL, and small sites, fits within that scope.

Pricing and which plan fits

If you already work with an AI coding tool and can change code yourself, Vibe Coding Hosting Basic is NT$3,588 billed yearly, an average of NT$299 a month. It includes one site, one address, one custom domain, a database, MCP access and automatic backups. If you'd rather tell an AI what to change after the move, Vibe Coding Hosting Pro is NT$11,988 billed yearly, an average of NT$999 a month, and includes Roamer AI, which does its best with migrated code but can't guarantee results. Both plans are billed yearly only, are set up about a minute after payment, and every new purchase can be fully refunded within 30 days. See the difference between them under Vibe Coding Hosting plans and pricing.

Frequently asked questions

Can I still download my data after December 10?

According to the announcement, read-only mode starts on December 10, SQLite and blob storage are not part of it, and the remaining services run until January 10, 2027. The announcement doesn't list which exports still work during read-only mode, so the safest plan is to download your code, environment variables and data before December 10.

Can I upload my vals without changing them?

No. Val Town runs on Deno and Vibe Coding Hosting runs Node.js, so at minimum you need a server that listens on PORT, and packages imported by URL have to move into package.json. Plain HTML and CSS files can go up as a static site as they are.

Can several vals share one plan?

Yes, as separate routes in one project, sharing one address and one database. Each plan holds one site, and multiple subdomains on one plan aren't supported.

Can I pay from outside Taiwan?

Yes. Plans are billed yearly in Taiwan dollars, and cards issued outside Taiwan work as long as they pass 3D Secure verification. Company invoices with a tax ID are available at checkout.

Sources

Ready to get started with Vibe Coding Hosting?

60 seconds after you subscribe, Vibe Coding Hosting is installed for you — an isolated container with hard resource limits you never share, and HTTPS out of the box.

Billed yearly · 30-day money-back guarantee · cancel renewal anytime

Hi, I'm Roamer! Tap me anytime with a question and I'll help you out.

Roamer

Roamer - AI assistant

Online
Roamer

Ask me anything, anytime — I'll do my best to help!

Powered by RoamerHost AI