Application Registry
The registry is where your organization's applications live. Every version, every review, every approval, every note — all in one place. Upload a ZIP file, and MeshOS takes it from there.
What the registry does for you
Most organizations have no single answer to "what does this application look like right now?" Code lives in repos, documentation drifts, reviews happen in Slack, and nobody knows which version is actually deployed.
The MeshOS registry solves this. Every application gets a home: versioned history, objective readiness scores, team notes, approval workflows, and a link to where it's deployed. Over time, it becomes your organization's ground truth about every application you own.
Submitting an application
Upload any application as a ZIP file containing source code. MeshOS supports TypeScript, JavaScript, Python, Go, Rust, Java, C#, Ruby, PHP, and more. Files up to 500MB.
Via the dashboard:
- Navigate to Submit Application
- Drag and drop a ZIP file or click to browse
- Add a name and description
- Click Submit — analysis begins immediately
Analysis typically completes in 2–5 minutes. You'll see real-time progress as each stage completes.
Via the API: Use the POST /applications endpoint with your API key and the ZIP file as a multipart upload. See the API reference for details.
Application lifecycle
Applications move through a defined lifecycle:
| Status | What it means | |--------|---------------| | Submitted | ZIP uploaded, analysis queued | | Analyzing | Static analysis and AI review running | | Analyzed | Complete — awaiting human review | | Under review | A reviewer is actively reviewing | | Approved | Cleared for deployment or promotion | | Archived | No longer active (data preserved) |
Approval is per readiness dimension — an application can be approved for cloud deployment but not yet approved for library promotion.
Version history and comparison
Every upload creates a new version. Submit the same application repeatedly as it evolves and the registry tracks the full history.
Compare any two versions to see exactly what changed: lines of code delta, new and deleted files, score changes across all three readiness dimensions, newly introduced findings, and findings that were resolved.
Teams use version history to hold each other accountable. When a score drops, the comparison view shows exactly what changed and why.
Team collaboration
Notes, concerns, and recommendations live alongside each application in the registry. Team members can leave pinned notes for critical issues, mark notes as resolved when addressed, and tag colleagues for input.
Note types — general, technical, concern, and recommendation — help categorize feedback so nothing gets lost in a sprint's worth of Slack messages.
Search
Search across all applications by name, description, status, readiness score, or tags. Semantic search finds applications and code patterns by meaning — search for "JWT authentication middleware" and find every implementation in your portfolio, not just the ones with "JWT" in the filename.
Domain tracking
Link each application to its deployed URL and environment. MeshOS monitors domain health and flags when the deployed version no longer matches the approved version — a simple but powerful check that many teams never have.
Audit trail
Every change to every application is logged immutably: who submitted it, who approved it, what changed, when. The audit trail can't be edited or deleted. This is your compliance record.
See the full API reference → Learn about readiness scoring →