AnythingCloud
Object storage, JavaScript Workers, and edge networking, built on S3-compatible storage. Instances add virtual servers with SSH access, extra volumes, and optional public IPs.
AnythingCloud gives every bucket a real S3 endpoint at
<bucket>.s3.anything-cloud.com. You can use the
console to upload files and manage folders, or point an AWS SDK at the
endpoint with your access keys. Workers run JavaScript on AnythingCloud's
managed edge, with their own addresses, triggers, bucket bindings, and
key-value store. TiniDB adds managed SQLite databases with a SQL editor, an
HTTP API, and Worker bindings.
Add a root domain, verify it with a TXT record at
_anythingcloud.<root>, point
*.<root> at edge.anything-cloud.com
(DNS only), then route any subdomain to a bucket or worker. For a deeper
name such as assets.eu.<root>, add a wildcard for that
branch too.
Instances run services that need a full server. Volumes add storage, and public IPs provide a stable address.
Cloud is opt-in and billed from your account balance. Verify your email address and add funds before enabling it, and keep a positive balance to keep resources running.
Instances
Create a virtual server, connect over SSH, and manage its firewall, disks, and snapshots.
Volumes
Block storage you can attach to a stopped instance.
Public IPs
Reserve a dedicated address and bind it to an instance.
Buckets
Create a bucket, upload files, make folders, and manage versions.
S3 Pages
Serve a static site from a bucket on a custom domain with automatic TLS.
S3 API
Use the endpoint, access keys, and signed requests from any S3 SDK.
Custom domains
Verify a root domain with TXT, point wildcard DNS at the edge, and route subdomains.
Workers
Run JavaScript on a request, a schedule, or a console object change, with environment variables and bucket helpers.
KV namespaces
Key-value namespaces with TTL, metadata, prefix listing, import and export, bound to workers when needed.
TiniDB
Managed SQLite databases with a SQL editor, HTTP API, scoped tokens, and Worker bindings.
Billing & metrics
Pay as you go or choose a monthly plan, and watch usage over time.
Quick start
- Open Tools and enable AnythingCloud. Your email address must be verified and your balance above zero.
- Create a bucket in Object storage → Create bucket. Pick a globally unique name and a billing mode.
- Upload files from the bucket page, or open Access to copy the S3 endpoint and keys.
- To publish a static site, open the bucket's Pages tab, choose the index and error documents, and follow S3 Pages.
- Optionally add a root domain under Networking, verify the TXT record, point
*.<root>at the edge, then route a subdomain to a bucket, worker, or database. - To run code, open Workers, create a worker, paste or upload a JavaScript module, and deploy it. Add request hosts, schedules, or object events on the worker's Triggers tab.
- To run a full server, add an SSH key under Key management, open Instances, create an instance, and connect from its Shell tab or with the SSH command on its Networking tab.
- For a relational store, open TiniDB, create a database, and query it from the console or the HTTP API. Create a token on its Access tab before connecting an application.
Endpoints
Each bucket has a generated endpoint. It serves public reads when the bucket is public, and signed reads and writes in both cases. A custom host replaces the generated endpoint in the console; the bucket page shows the active one:
https://<bucket>.s3.anything-cloud.com
The generated endpoint uses virtual-hosted addressing, so the bucket name
is part of the hostname. A custom host is used with path-style addressing
instead. The region is us-east-1. The S3 API guide covers
credentials, SDK setup, and presigned links.
What is included
| Feature | Details |
|---|---|
| Buckets | Five per member by default. Request a higher limit from Settings. Plans include 5, 100, or 250 GB storage. |
| Workers | JavaScript request handlers on a managed edge, with schedules, object events, environment variables, and bucket bindings. |
| Instances | Virtual servers with a boot disk, SSH access, a browser shell, firewall rules, metrics, and snapshots. Early access. |
| Volumes | Extra block storage for an instance. Attach during instance creation, or while the instance is stopped. Data stays when the instance is deleted. |
| Public IPs | Dedicated IPv4 addresses bound to one instance each, or attached to a dedicated TCP load balancer. Billed while reserved. |
| Load balancers | Spread a hostname or public IP across running instances. Shared and dedicated plans; see Load balancers. |
| SSH keys | Generate an Ed25519 pair or import an existing public key. Choose a default for new instances. |
| KV namespaces | Key-value storage with TTL, metadata, prefix listing, and import/export. Create it without a worker and bind it when needed. |
| TiniDB | Managed SQLite databases with a SQL editor, scoped API tokens, an HTTP API, and Worker bindings. Limits and usage are in Settings. |
| Object browser | Folders, multi-file uploads, ETags, details, rename, and delete. |
| Versioning | Keep old versions and restore them from an object's details. |
| S3 Pages | Serve a bucket as a static site with index and error documents on a custom domain. See S3 Pages. |
| Custom domains | Verify a root domain with TXT at _anythingcloud.<root>, point *.<root> (or the branch wildcard for deeper names) at the edge, then add a host and route it to a bucket, worker, or database. |
| Edge features | WebSockets and exploit-path blocking for bucket routes, plus per-host and per-client rate limits. |
| Edge cache | Per-host rules that set how long each file extension stays in the edge cache, with 5-minute to 1-year TTLs or no caching at all. |
| Traffic analytics | Requests, cache hit rate, bytes served, and errors across all hosts, with per-host breakdowns and 24-hour, 7-day, and 30-day charts. |
| Metrics | Storage, reads, and writes over 24 hours, 7 days, or 30 days, plus per-worker request and runtime metrics and per-instance processor, memory, disk, and network charts. |
| Billing | Pay as you go billed continuously, monthly storage plans, and a monthly spend budget with optional hard cap. |