# OnSide > OnSide is an always-on service and software platform that keeps your regulatory and compliance documentation current. It is a LeapFI platform. OnSide sits between the regulators and your stack: regulatory sources on one side, the systems your team already works in on the other. It monitors regulatory bodies and changes in law, drafts the updated language when a gap opens, routes it through your approval chain, and — once approved — versions the policy live and notifies connected systems. Exam-ready is the resting state. ## Key pages - [Home](https://onside.leapfi.ai/): Product overview — the problem, the signal, the compliance loop, the platform, and getting started. ## Why OnSide - Your policies go stale the moment a regulator moves. Every institution runs on complex policies and procedures, and each one is out of date the moment a rule changes. - Today someone has to monitor, read, interpret and rewrite — slow, expensive, and always a step behind. - OnSide finds the changes that matter to you and watches each gap until it closes. ## The Signal A heartbeat between the regulators and your stack. OnSide sits in the middle. Regulatory sources on one side, the systems your team already works in on the other. Detected at the source, drafted in your language, written back where your team already works — nothing changes until you approve it. Regulatory sources monitored include: OCC, FDIC, Federal Reserve, NCUA, CFPB, FinCEN / OFAC, SEC / FINRA, FFIEC (NIST), state regulators, executive orders, and state & municipal law. It writes back into your GRC stack: SharePoint, Ncontracts, Archer, Confluence, Box / Drive, or your own repository. ## The always-on compliance loop Monitor, propose, approve, version, enforce and rich reporting — the loop never stops: 1. Monitor: OnSide tracks regulatory bodies and changes in law, surfacing obligations and strategic shifts. 2. Detect: It flags when a policy should change, when a rule opens a gap, or when a signal may impact your current strategy. 3. Propose: It drafts the updated language and routes it through the right approval chain for that requirement. 4. Version: Once approved, the prior policy is archived, the new version goes live, and connected systems are notified. 5. Enforce: The APIs and MCP server only ever serve the active policy, so anything you build stays compliant. 6. Report: A clear audit trail of every change and approval, shaped into board-ready reporting. ## Policy as a live system of record OnSide turns a static document library into something queryable. Every product, integration and AI agent you build reads from one source that is always current. - MCP Server: your rules, readable by agents. A Model Context Protocol server exposes your current policies and procedures, so any AI agent you deploy can ask what the institution's rules actually are, right now. - APIs: one version of the truth, always. Exposed APIs integrate with existing platforms and systems, giving everyone the same, current record — compliance becomes part of your DNA, instead of a quarterly project. ## The working surface Inside OnSide is a working surface across dashboard, posture, regulatory feed, documents, cases, proposed (redlined) language, and third-party & vendor risk. ## Our sources Monitored separately, because obligations stack: - Banking regulators (financial): OCC, FDIC, Federal Reserve, NCUA, CFPB, state regulators. - Governing agencies (systemic): OFAC, SEC / FINRA, FFIEC (NIST), FinCEN, FHFA. - National & state (regional): White House executive orders, bills moving through government, state governments and laws, municipal governments. ## Five steps, starting from whatever you have 1. Share your current state: policies, procedures and evidence in whatever shape they are already in — Word files, PDFs, scans, spreadsheets, board minutes. OnSide connects to your repository or holds a secure copy. 2. Build a baseline: one clear picture of where you stand, measured against financial-services risk and AI governance standards. 3. We monitor regulators: federal guidance, state law, local ordinances, the risk frameworks and your own documents — each layer watched on its own. 4. Early alerts and suggestions: the moment something moves on any layer, your whole document set is checked. You see what changed, where it came from, and what it touches. 5. We propose, you approve: every gap arrives with proposed language, reviewed by the risk team first. Nothing changes until you say so. ## Three things improve immediately - Hours back: the reading, cross-referencing and hunting for affected policies stops being someone's job. What is left is the judgement. - Exam-ready: sources monitored and documentation kept current, so there is no history to reassemble from email threads. - One answer: a single current view of where the institution stands, in language a board can act on, without anyone building a deck for it. ## See OnSide on your own policies Bring one policy set. We will show you what moved, what it touches, and the language we would propose. ## Contact - Request a walkthrough: https://www.leapfi.ai/#contact - Parent company: https://leapfi.ai/ ## Optional - Full sitemap: https://onside.leapfi.ai/sitemap.xml Illustrative content; not legal or compliance advice. © 2026 LeapFI LLC.