Projects
A project is one application. It holds the source, its environments, its releases and its review policy.
Product
Shipvise is a small number of concepts that fit together. Here is what each one does today.
Availability reflects the current state of the public beta.
A project is one application. It holds the source, its environments, its releases and its review policy.
Every change is captured as a revision with an author, a description and a diff, whether it came from a commit, an upload or an agent.
Each project gets isolated environments with their own resources, variables and URL.
A place to run the change and use the application before deciding anything about production.
Production is only ever updated by promoting a release that already exists, after an explicit approval.
Point your own domain at a production environment with managed certificates.
Build, container start, healthcheck, secrets detection, dependency scan and required configuration.
AI review and senior review, requested per release, returning structured findings rather than a pass or fail flag.
An immutable artifact plus everything that happened to it: checks, reviews, deployments and approvals.
Build and runtime logs with severity filtering and search, streamed while a deployment runs.
Return production to a previous release without rebuilding anything.
Environment variables per environment. Secret values are write-only in the interface and are never returned to the browser.
Create a workspace, connect a project and deploy it to staging. Decide about production when you have seen it running.