Configure Pixeltable Cloud: pixeltable.toml, Secrets, and Deploy Order

Pixeltable Cloud, currently in limited beta, lets users deploy the same `app.py` used locally to a hosted database and separate HTTP service runtime, configured through a Pixeltable project entry in `pixeltable.toml` or `pyproject.toml`. Deployment generally proceeds by updating the database and project files with `pxt db update`, applying table schema changes with `pxt schema update`, and starting or refreshing routes with `pxt service update`; the database handles catalogs, table operations, and indexing, while the service handles FastAPI routes. Configuration controls included project files, Python version, dependencies, system packages, database resources, and local media-cache disk, while source-only changes upload quickly and dependency changes trigger slower image rebuilds. Cloud databases provide a default home storage bucket for media, with options for local-to-cloud transfers or external S3, GCS, and Azure destinations. Provider credentials are stored as organization or database secrets and require process restarts to take effect, whereas Pixeltable API keys authenticate CLI use, backends, and hosted service requests, with optional scoped grants in preview. Operational commands support status checks, logs, restarts, stops, image rebuilds, and deletion, and the platform emphasizes keeping service URLs dynamic, retaining API keys on servers rather than browsers, and using the same application file across local and hosted environments.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.