Enterprise
Onboarding Process
Production API access, custom connectors and dedicated environments require a structured onboarding engagement. Here is exactly how it works — from first call to production deployment.
Four phases to production.
Discovery
We work with your compliance team to understand your regulatory obligations, sector context, data sources and current workflows.
Deliverables
- Sector & regulatory scope confirmed (AMLA, MiCA, DORA, AI Act…)
- Data sources and formats inventoried
- Internal stakeholders identified
- Compliance use cases prioritised
- Integration requirements documented
Data Mapping
Your internal field names and data structures are mapped to the ReguShield compliance schema. You do not need to rebuild your data model.
Deliverables
- Column / field mapping table produced
- Sample data set reviewed and validated
- Data format confirmed (CSV / Excel / PDF / API / DB export)
- Schema normalisation rules agreed
- Sector-specific risk fields configured
Pilot Validation
We run your actual data through the compliance engine in your dedicated pilot workspace. You review AI reasoning, risk scores and regulatory mapping outputs.
Deliverables
- Pilot workspace provisioned with your workspace ID
- First data set uploaded and analysed
- AI reasoning and regulatory output reviewed
- False positives / edge cases discussed and tuned
- Executive report format validated
Production Rollout
Production credentials are issued, integration connectors configured, SLA agreed and ongoing support channel established.
Deliverables
- Production API keys and webhook secrets issued
- Integration connectors deployed (API / DB / SharePoint / SAP…)
- SSO configuration if required
- SLA and data retention terms agreed
- Dedicated Slack / Teams support channel set up
You bring the data.
We bring the compliance layer.
ReguShield AI handles the regulatory complexity. Your team focuses on business decisions.
No data model rebuild required.
If your data is not in our standard template — we map it during onboarding.
Start with a pilot, not a commitment.
CSV/Excel pilot analysis starts within 24 hours of access approval — no connector setup required. Enterprise integration is layered on after pilot validation.
Request Pilot Access →Security, isolation and compliance by design.
Every ReguShield deployment — pilot or enterprise — operates with these controls in place.
Data Isolation
Every tenant workspace is isolated by a unique workspace ID enforced at the database, API and authentication layers. No data is shared across customers.
Authentication
Supabase email/password authentication with admin approval gate. Every pilot access request is manually reviewed before workspace credentials are issued.
Audit Logs
Every upload, case status change, AI copilot interaction and API call is logged with user identity, workspace ID, timestamp and outcome. Immutable audit trail.
Environment Secrets
All service credentials — Supabase, OpenAI, API keys — are protected as server-side environment variables. No sensitive keys are ever exposed to the client.
Compliance Decision Support
ReguShield AI is decision-support infrastructure — not legal advice and not a substitute for qualified legal counsel. Output should be reviewed by your compliance team.
Enterprise Onboarding
Production API access, custom connectors and dedicated environments require an onboarding engagement — security review, data field mapping and customer approval before deployment.
Onboarding questions
What if our data is not in CSV or Excel?
We handle it during onboarding. ReguShield maps your fields to our compliance schema whether your data is in PDF, a database export, an API feed, or a cloud folder. You do not need to rebuild your data model.
How long does the onboarding process take?
CSV/Excel pilot access starts within 24 hours of approval. Full enterprise integration (API connectors, SAP, SharePoint, etc.) typically takes 2–4 weeks depending on complexity.
Do we need our own compliance team?
Recommended. ReguShield provides compliance decision-support infrastructure, not legal advice. Output should be reviewed by your compliance officer or legal counsel.
Is production API access available immediately?
No. Production API access requires a security review, data field mapping and customer approval. A pilot API sandbox is available for technical evaluation before that commitment.
What regulations does ReguShield cover?
AMLA 2027, AMLR, AMLD6, MiCA, DORA, EU AI Act, Travel Rule and FATF recommendations — across FinTech, Crypto/CASP, AI companies, EMIs, Payment Institutions and Banks.
What happens after production rollout?
You receive a dedicated support channel (Slack or Teams), SLA-backed uptime, regulatory framework updates as legislation evolves, and an ongoing customer success contact.
Ready to start the conversation?
Send us your sector and data format — we will scope the onboarding in one call. No commitment required to start a pilot.