Built with Nuxt and Vue.js, hosted on Cloudflare. Domain registered in 2026.
weeny.cloud is built with Nuxt, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics. It sends email through Amazon SES.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| – | 6 Nov 2026 | |
| – | 6 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 6 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting1 | ||
| – | 6 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 6 Nov 2026 | |
| Transactional Email2 | ||
| – | 6 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 6 Nov 2026 | |
| Security, WAF & Bot Protection1 | ||
| – | 6 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
mx02.mail.icloud.commx01.mail.icloud.comval.ns.cloudflare.comcarter.ns.cloudflare.comapple-domain=Jyit8PLuAUf8gjqUv=spf1 include:_spf.mx.cloudflare.net include:icloud.com ~allgoogle-site-verification=HzMS6qc6p4ALC4qE450uJatYB9iJm-SuwqiuR9PdEAwv=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;# Search engines and AI assistants are welcome here. weeny is a cloud for coding # agents — agents finding and reading these docs is the point, not a side effect. # Machine-readable docs: /llms.txt · /llms-full.txt · /weeny-skill.md · /recipes/ User-agent: * Allow: / Disallow: /dashboard Disallow: /admin Disallow: /login # Named explicitly: Cloudflare's managed robots.txt disallows these by default. # Retrieval bots (a user or agent asked for this page) and search indexers. User-agent: Claude-SearchBot Allow: / User-agent: Claude-User Allow: / User-agent: OAI-SearchBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: PerplexityBot Allow: / User-agent: Googlebot Allow: / User-agent: Bingbot Allow: / # Brave runs its own independent index — and it's the one Claude's web search reads, # so it matters more to us than its market share suggests. User-agent: Bravebot Allow: / User-agent: Yandex Allow: / # Training crawlers. Allowed deliberately: weeny wants to be in the corpus that # coding agents are built from — that is a distribution channel, not a leak. User-agent: ClaudeBot Allow: / User-agent: GPTBot Allow: / User-agent: Google-Extended Allow: / User-agent: CCBot Allow: / Sitemap: https://weeny.cloud/sitemap.xml
# weeny.cloud — a real Linux server for your agent > Build it. Put it on the internet. Keep it free forever. > Start with seven days at 4GB, then keep the same server at 1GB free forever. > No card, no automatic charge; your apps and data stay. Free servers sleep after > 30 idle minutes and wake on the next request. Weeny gives coding agents a persistent Linux server with root, SSH, systemd and a package manager. Run your own stack: Node, Python, Go, SQLite, Postgres, Docker. Deploy apps with public HTTPS URLs, private sharing, encrypted app configuration, logs, rollback and off-machine backups included. Paid always-on plans start at $3/month (founding prices), with flat pricing and no usage metering. ## From code to a live URL Run these **on the user's computer**: ```sh npx weeny-cloud login # email + 6-digit code from the user's inbox npx weeny-cloud create # server ready in about 2 minutes npx weeny-cloud push ./myapp myapp --build "npm ci && npm run build" -- npm start npx weeny-cloud ssh "weeny expose myapp 3000" ``` Give the user the returned HTTPS URL. A push uploads your code, builds a fresh release, health-checks it and switches it live. If a build or start fails, the previous release keeps serving. Re-deploy with `npx weeny-cloud push ./myapp myapp`; the build and start commands are remembered. Use your app's own commands for other languages, or omit `--build` for a ready-to-run app. `create` starts with seven days at 4GB, then automatically continues free forever at 1GB. `create --free` starts directly at 1GB and skips this account's trial. Login only signs in; it does not provision a server. Use the account's returned status if creation needs a retry or another step. The user chooses any paid plan. ## Two CLIs, one simple workflow - **On your computer:** `npx weeny-cloud` handles login, create, push, SSH and app discovery. - **On your Weeny server:** `weeny` handles deploy, expose, env, sharing and rollback. - Run either CLI with no arguments for next steps, or use `help <command>`. - Install the agent guide with `npx weeny-cloud skill`. Working directly on the server? Keep source in `/workspace/myapp` and run `weeny deploy myapp --build "<build command>" -- <start command>`, then `weeny expose myapp <port>`. Each app needs its own port. ## Included app operations - **Private sharing:** `weeny expose myapp 3000 --private`, then `weeny allow myapp amy@example.com` or `weeny allow myapp @company.com`. Weeny handles email sign-in; your app receives the visitor in `X-Weeny-User`. - **App secrets:** `weeny env myapp KEY=value` stores encrypted configuration and injects it at startup. Set required secrets before the first push. - **Release history:** `weeny inspect myapp`, `weeny releases myapp` and `weeny rollback myapp`. Rollback restores code and start commands; data and env stay. - **Logs:** `journalctl -u weeny-myapp -f`. `weeny restart myapp` restarts the current release; push or deploy to publish changed code. - **Shared apps:** `npx weeny-cloud apps` lists your apps and apps shared with you. `npx weeny-cloud token <host>` gives an allowed caller a bearer for private apps. - **Custom domains:** included with paid plans; `weeny domain myapp app.example.com`. ## Keep app data across releases Store databases and uploads in `$WEENY_DATA_DIR` (`/data/<app>`), outside the release directory. Deploy and rollback leave that data in place. Free servers restart apps when they wake; keep persistent state on disk. For an always-running worker, choose an always-on plan with the user. ## Recipes and references - Start here: https://weeny.cloud/recipes/default.txt — Node + SQLite, any frontend. - Framework builds: https://weeny.cloud/recipes/nextjs.txt - Local builds for 1GB servers: https://weeny.cloud/recipes/teeny.txt - Python: https://weeny.cloud/recipes/python.txt - Postgres: https://weeny.cloud/recipes/postgres.txt - n8n: https://weeny.cloud/recipes/n8n.txt - Docker: https://weeny.cloud/recipes/docker.txt - Streaming and background jobs: https://weeny.cloud/recipes/long-running-requests.txt - Full command and operations reference: https://weeny.cloud/llms-full.txt - Agent skill: https://weeny.cloud/weeny-skill.md - Server and billing API: https://weeny.cloud/agent-api.md - Human-readable docs: https://weeny.cloud/docs Each Weeny app describes itself at `GET /__weeny`. Add an `llms.txt` to your app's source to publish its purpose, endpoints and authentication alongside each release. Private app docs follow the app's access list.
| – |
| 6 Nov 2026 |
| – |
| 6 Nov 2026 |