Built for compliance professionals who know what's actually broken.

The pilot takes about 45 minutes. Here's exactly what we'd like you to work through:

1. 1Create your account and set up your organization profile
2. 2Upload at least one compliance document — a policy, SOP, or internal procedure your company uses
3. 3Review what Olivra extracted from your document — does the company profile look accurate?
4. 4Review your regulatory scope — does it reflect how your company actually operates?
5. 5Walk through your Olivra-generated compliance program — does the structure make sense for your work?
6. 6Review the health score for your program — is it meaningful and fair?Your compliance health score (0–100) measures how complete your program is against a 9-section trade compliance standard. Each section is checked for 5 required elements: an assigned owner, auditable evidence, a review frequency, an escalation path, and regulatory traceability. Every element found adds to the score. A score of 100 means your program covers all 45 required elements.
7. 7Note anything that confused you, felt wrong, or that you would want to change
8. 8Explore your training modules and sign the program attestation
9. 9Review the oversight dashboard and monitoring status

Over the following week, Olivra monitors regulatory sources relevant to your trade profile in the background. If changes are detected, you'll receive a compliance digest email automatically. One week after your setup, Andres will reach out to schedule your Session 2 check-in.

Don't have a document you can upload? Email andres@olivra.io and we'll send you a sample document to use for the pilot — no real company data required.

Once you're signed in, look for the Feedback button pinned to the bottom-right of every Olivra page. Use it as often as you need to — for bugs, confusion, missing pieces, or rough edges. Each submission goes straight to Andres, so you don't need to wait for the follow-up call.

• Pick a category: Something's wrong with the AI, a regulation or program issue, design or navigation, or a missing feature. This helps route fixes to the right place.
• Describe what you ran into: A sentence or two is plenty. Specifics help — which page you were on, what you expected, and what you saw instead. The page you were on is captured automatically.
• Flag if it's blocking you: Check the "This is preventing me from using Olivra" box if you can't continue the pilot until it's fixed. Blocking issues get worked first.

Prefer email? Anything you'd send through the widget can also go to andres@olivra.io. Both reach the same inbox.

We understand that compliance documents are sensitive. Before you upload anything, here is exactly how Olivra handles your data:

• Company isolation: Your organization's data is completely separated from every other company on the platform. No cross-company access is possible at the database level or the application level.
• Access controls: Only authenticated members of your organization can access your documents, program, and audit trail.
• Encrypted in transit: All data is protected with HTTPS/TLS encryption.
• No AI training: Olivra does not use your uploaded documents to train AI models. Your documents are processed to generate your compliance program and nothing else.
• Who can see your data: As the sole operator of Olivra, Andres Gonzalez (founder) has infrastructure-level access to the platform. Your documents are not reviewed, accessed, or shared. This is standard for early-stage SaaS and will be governed by formal access controls as the platform scales.
• Certifications: Olivra does not currently hold SOC 2 certification. The platform is built toward those standards and certification is on the roadmap as we scale beyond pilot.
• Data location: Your data is stored on Supabase infrastructure hosted on AWS (US East region).

For the full technical security architecture, visit our Security & Trust page.

Olivra monitors 40+ live regulatory sources — including Federal Register, BIS EAR, OFAC SDN, CBP Customs Bulletin, EUR-Lex, CBSA, and WCO. Every source, its coverage scope, and its last check timestamp are visible in the Sources tab of your dashboard. We know coverage gaps matter. During the pilot, one of our specific asks: which sources does your team rely on that you don't see here? Your answers directly shape what we add next.