Turn a static build into a live space.

Deploy from a folder, CLI, or API. Add scoped data, private files, message history, and AI routes for trusted server code.

Static output folderPrepared locally before deployment
CLI
Agent API
Manifest
Manifest
PathTypeSizeCache
index.htmlhtml1.2 KBrevalidate
assets/app.jsjs8.7 KBhashed
assets/styles.csscss2.1 KBhashed
assets/logo.svgfile3.3 KBhashed
manifest.jsonjson1.1 KBverified
Attached runtime
DataScoped access
FilesScoped access
RealtimeScoped access
AIScoped access

Everything your app needs, attached.

Data

Store and read JSON records through scoped runtime routes.

Files

Keep private uploads and generated assets behind service tokens.

Realtime

Publish events and read channel history through the SDK.

AI

Call managed text generation from trusted server code.

Built for how you ship.

Start with your built static output. The CLI or deployment API validates a manifest and stores the assets for a static delivery path.

CLI
$ deploylet deploy ./dist --config deploylet.config.json

Validating allowed files and paths
Generating deployment manifest
Reporting file hashes and byte counts

Agent-ready by default.

Deploylet exposes the same publishing flow to humans and agents: explicit JSON responses, scoped write tokens, discoverable docs, and recoverable errors.

JSON in/out

Agents get explicit responses with URLs, status, and next actions.

OpenAPI

Every deploy and runtime route stays visible as a machine contract.

llms.txt

Keep the short integration path discoverable for coding assistants.

Scoped tokens

Give agents the narrow deploy or runtime capability they need.

Built around narrow access. Not broad claims.

Static delivery is straightforward. Runtime access is deliberately constrained so browser and server code can do only what they need.

Scoped runtime tokens and token revocationEnvironment and allowed-origin scopingPrivate file access for service tokensManifest verification before asset storageSafe endpoint checks in the CLI and SDKDefault exclusions for common secrets and source maps

Give every build a live, managed space.

Share your use case, deployment path, and expected runtime needs. We are onboarding private-beta teams directly.