Metadata memory
Capture Salesforce metadata changes over time with the Org360 Memory Collector.
Interact with Agent Org360 where you work
Microsoft Teams
Ask from any Teams conversation.
Coming soonCLI
Query metadata from the terminal.
Coming soonThe Memory Collector tracks how your org evolves, while Agent Org360 helps you reason over that history.
Capture Salesforce metadata changes over time with the Org360 Memory Collector.
Run 40+ prechecks that surface metadata risks, prioritize fixes, and help optimize your org health.
Connect every change to affected fields, flows, validation rules, permissions, and related metadata.
Ask what changed, why it matters, and how to safely respond.
Keep metadata history in your org with a managed package designed for trust.
Use Org360 AI, bring your own model key, or connect a local/private model later.
Install the Org360 Memory Collector managed package in your Salesforce org.
A daily job captures setup activity and enriches it into metadata deltas.
Org360 stores a structured history of what changed and when.
Use the Org360 assistant to understand impact, risk, and recommended next steps.
Claude Code with a Salesforce MCP server is a great way to inspect your org on demand. Org360 solves a different problem: your org changes every day, and a one-shot scan has no memory of what it looked like yesterday. And because Org360 is cache-first, it answers from a stored metadata snapshot instead of hammering your org's API limits on every question.
| Claude Code + Salesforce MCP | Org360 | |
|---|---|---|
| Salesforce API usage | Fires many live API calls on every question — burns your org’s daily API limit and adds latency. | Cache-first: ~150 calls once per scan, then thousands of answers from memory at near-zero API cost. |
| How it works | You ask; the agent reads the current state of your org. | A daily collector captures changes automatically, overnight. |
| Metadata history | No memory between sessions — each conversation starts fresh. | Structured timeline of every enriched delta, stored in your org. |
| "What changed yesterday?" | Not answerable — there's no record of what the org looked like before. | Core question. Answered with source, risk, and dependency context. |
| Impact analysis | Can describe current dependencies if you know which component to ask about. | Every change is automatically linked to affected flows, rules, and fields. |
| Data lives | In the conversation context — gone when the session ends. | In your Salesforce org (managed package) and optionally Org360 Cloud. |
| Best for | Ad-hoc exploration, one-off analysis, writing Apex or queries. | Ongoing change governance — knowing what changed and what to do next. |
The two tools are complementary — Org360 gives your AI assistant a structured metadata memory to reason over, instead of a one-time read of the current state.
Start with one Salesforce org and 50 prompts. Upgrade when you need multiple orgs, more Agent Org360 usage, and team collaboration.
Try the full Org360 experience on one Salesforce org, capped for personal evaluation.
Scale Org360 across multiple Salesforce orgs with team collaboration and monthly prompts per org.
Advanced privacy, BYOK/local models, longer retention, integrations, security surface analysis, and team governance.
Private beta pricing — checkout is available for invited beta testers. Try it free →
The managed package can store metadata history inside your Salesforce org, while optional cloud services enrich changes and power the assistant. Enterprise customers can use stricter retention, BYOK, local/private model options, and controlled sync modes.
See how the collector worksThe product design is metadata-first. The core use case does not require Accounts, Contacts, Opportunities, Cases, or other business records.
No. Agent Org360 is strictly read-only. It reads metadata to analyze, explain, and surface recommendations — but it never writes, updates, or deletes anything in your Salesforce org. Every action stays in your hands.
The package creates a trusted metadata memory inside Salesforce and can capture daily change signals without relying only on a one-time external scan.
No. The durable value is the metadata memory layer. The assistant is the interface that helps you ask useful questions about that memory.
The planned Enterprise path includes BYOK and private/local model options.