Operating Vista Platform¶
Documentation for deploying and running Vista Platform — solutions engineers, platform operators, and anyone standing up the platform for their own organization.
Quick Start¶
| I want to… | Start here |
|---|---|
| Try it, evaluate it, or deploy it for real | INSTALL.md at the repository root — three paths (laptop, single VM, production cluster), plus how to verify the images |
| Stage internal service-mesh mTLS on a production cluster | Service-mesh mTLS |
| Run a production pre-flight | Production Checklist |
| Operate the platform day-to-day | Platform Admin Guide |
| Back up the platform, see whether a new release is out, or update it | Maintenance in the admin console |
| Keep the end-of-life and vulnerability catalogues current (including air-gapped) | Platform catalogues and their feeds |
| Monitor and alert | Monitoring Setup |
| Work out which legal documents are yours to write | Legal documents for operators |
| Troubleshoot issues | Common Issues |
Contents¶
Deployment¶
INSTALL.mdat the repository root — Try it / Evaluate it / Run it, and image verification- Production Checklist
- Service-mesh mTLS — staging internal mTLS across upgrades, managed-Postgres/NATS notes
- Database Migrations
- Rating vocabulary upgrade — Coordinated API/schema changes, reassessment and evidence limits
- Device Agent Deployment
Operations¶
- Platform Admin Guide — Complete operations reference
- Maintenance in the admin console — Backups and restore, update notices, one-click update and rollback
- Releases — Release process, versioning, upgrade path
- Startup & Shutdown — Service lifecycle management
- Container Runtime Images — Source of truth for all runtime images
- Platform Catalogues — End-of-life and vulnerability data: the mirror feeds, their rate limits and attribution, and the offline bundle for air-gapped installs
- Notification Providers — Slack, Email, Webhook, PagerDuty
Legal¶
- Legal documents for operators — who is responsible for what when the software is self-hosted, and how click-through acceptance is recorded
- Data Processing Agreement template — for when you run a deployment on someone else's behalf, with the technical measures annex pre-filled
Monitoring¶
Security¶
Configuration¶
- Platform Integrations — AWS, Azure, GCP, SaaS CMDB integrations
- Connecting a model provider — optional; every AI capability has a rule-based default that runs without one
- Outbound connections — egress proxy (
HTTPS_PROXY), the egress NetworkPolicy, private endpoints and custom CA bundles for integrations