What is PreviewShip optimized for?

PreviewShip is optimized for fast frontend preview sharing rather than acting as a full production application platform.

How do machine workflows authenticate?

Machine-driven workflows use PreviewShip API keys in CLI, MCP, and editor integrations.

Security

Security starts with a narrower job: preview sharing

PreviewShip is intentionally scoped around getting built frontend artifacts into a shareable browser URL. Teams evaluating preview tools often care less about every cloud feature and more about whether the workflow is controlled, predictable, and easy to reason about.

Scoped product surface

PreviewShip is designed for preview sharing, not as a full production hosting control plane. That narrower product surface reduces operational complexity for the core workflow.

API-key based access

CLI, MCP, and editor workflows authenticate through API keys generated in the console. That makes it easier to separate machine access from browser sessions.

Explicit lifecycle limits

Preview expiry windows are part of the product model, which makes preview retention easier to reason about than ad hoc artifact storage.

What this page is and is not

This page is a public trust summary. It is not a substitute for a dedicated compliance program, formal security questionnaire process, or contractual documentation. It exists to make the product model legible before a prospect signs up.

If you need a support response tied to a concrete deployment issue, contact support directly so the problem can be handled in context.

Next step

If you are evaluating PreviewShip for a team workflow, read the guides and docs next. They explain exactly how API keys, CLI, MCP, and editor deploy flows behave in practice.

Browse guides Contact support