Data
Store and read JSON records through scoped runtime routes.
Deploy from a folder, CLI, or API. Add scoped data, private files, message history, and AI routes for trusted server code.
Store and read JSON records through scoped runtime routes.
Keep private uploads and generated assets behind service tokens.
Publish events and read channel history through the SDK.
Call managed text generation from trusted server code.
Start with your built static output. The CLI or deployment API validates a manifest and stores the assets for a static delivery path.
$ deploylet deploy ./dist --config deploylet.config.json
Validating allowed files and paths
Generating deployment manifest
Reporting file hashes and byte countsDeploylet exposes the same publishing flow to humans and agents: explicit JSON responses, scoped write tokens, discoverable docs, and recoverable errors.
Agents get explicit responses with URLs, status, and next actions.
Every deploy and runtime route stays visible as a machine contract.
Keep the short integration path discoverable for coding assistants.
Give agents the narrow deploy or runtime capability they need.
Static delivery is straightforward. Runtime access is deliberately constrained so browser and server code can do only what they need.
Share your use case, deployment path, and expected runtime needs. We are onboarding private-beta teams directly.