RenewalOS Local

RenewalOS Local is a free, open-source commercial P&C renewal intelligence workspace for independent agencies. It is designed to work beside EZLynx: EZLynx remains the system of record, while RenewalOS adds source-backed document review, change detection, exception routing, workflow coordination, and explicit licensed-user approvals.

No account, subscription, payment, installation ID, or activation code is required for the local edition.

Ready to begin? Follow the launch guide for the exact first-use workflow and a clear list of what is live versus what still needs integration credentials.

Included

• Responsive renewal dashboard, attention queue, workflow pipeline, and audit history
• New-renewal and controlled CSV-import flows
• Two-step CSV validation with a downloadable starter template and explicit save confirmation
• Secure, single-use client questionnaire links with attestation
• Local document storage and source-first extraction records
• Page-level review for verifying, correcting, or rejecting extracted policy fields
• Clearly labeled extraction simulator for testing before AI provider credentials are available
• Year-over-year change detection and exception review
• Quote normalization and comparison without carrier ranking
• Submission-readiness gate before controlled manual EZLynx handoff
• Approval records tied to a SHA-256 payload hash and immutable audit events
• Daily encrypted Windows backups with safe restore and ten-copy retention
• Adapter contracts for EZLynx, Microsoft Graph, Azure document intelligence, and licensed forms

Safety boundaries

• RenewalOS does not autonomously recommend, bind, send, or change coverage.
• A licensed user must verify AI-extracted values against the source and approve external actions.
• The source is public, but agency documents, customer data, credentials, and backups remain the operator's responsibility and must never be committed.
• EZLynx, ACORD, carrier, and AI-provider access still require the operator's own contracts, permissions, and credentials.
• State-specific notice logic remains inactive until entered from current primary sources and approved by insurance counsel.

Install on Windows

Download RenewalOS-Local-Setup.exe from the latest GitHub release and run it. RenewalOS installs for the current Windows user, keeps working data on that computer, and opens from a desktop or Start Menu shortcut.

Upgrades preserve the .wrangler working-data directory, create an encrypted pre-upgrade backup, stage and verify the new payload, and remove stale application files from earlier versions.

The tray menu can create or restore encrypted backups. Backups use Windows Data Protection and can be decrypted only by the Windows user who created them.

Run from source

Install Node.js 22 or newer and pnpm, then run:

pnpm install
pnpm run local

You can also double-click Start RenewalOS.cmd. Developers can use pnpm run local:dev for hot reloading. No cloud account or integration credentials are required for the guided local workflow.

Optional self-hosted Cloudflare deployment is documented in DEPLOYMENT.md. Hosted authentication and legacy billing adapters are separate from the free local runtime and are not required to use RenewalOS Local.

Integration checklist

1. Confirm EZLynx Connect/API eligibility, sandbox access, permitted fields, write-back behavior, and forms rights.
2. Register a Microsoft Entra application, scope mail access to the designated shared mailbox, and obtain tenant-admin consent.
3. Execute enterprise data-processing terms for any AI provider and prohibit training on agency data.
4. Add counsel-reviewed state rule records; do not convert AI output into legal deadlines.
5. Replace the guided agency bootstrap with a reviewed onboarding flow before a multi-agency hosted deployment.

License and contributing

Copyright (C) 2026 RenewalOS contributors.

RenewalOS Local is licensed under the GNU Affero General Public License v3.0 or later. You may use, study, modify, and redistribute it under that license. If you run a modified version for users over a network, you must offer those users the corresponding source as required by the AGPL.

Contributions are welcome. By contributing, you agree that your contribution is licensed under AGPL-3.0-or-later.

See PLAN.md for the product direction and remaining integration work.