Your regulatory repository,
brought to life.
Move beyond storing and searching documents. Compliance OS connects regulatory sources to your firm’s profile, applicable requirements, controls and reporting, giving your AI the context to help you work through them.
Built around Cyprus investment firm compliance.
For compliance officers and internal teams.
The workflow, from profile to operational requirements
The same rule can mean different things for different firms. Compliance OS connects the firm's recorded activities to its regulatory requirements, then to the controls and reporting that follow.
Build the company profile
Your permissions, services, client categories and business activities shape your regulatory position. The company profile gives those facts a structured home.
Questions distinguish recorded answers from facts that still need confirmation. Some inputs depend on an event; others require specialist judgement or need to be recalculated from underlying facts.
- Record the facts. Build the profile around the activities and characteristics of the firm.
- Keep uncertainty visible. An unanswered question is not treated as a negative answer.
- Review changes in context. A changed profile may affect the assessment that relies on it.
Confirming a profile fact and refreshing the applicability assessment are separate steps. The assessment needs to reflect the profile version you intend to use.
Assess which requirements apply
Move from a broad regulatory framework to the requirements relevant to a particular firm. Applicability brings together the recorded company facts, the conditions attached to a requirement and the assessment outcome.
When a decision depends on missing information or further review, that dependency stays visible. The aim is a clear explanation of the firm's position, including the questions still open.
- Follow the basis. Review the facts and sources behind a decision.
- Resolve the right question. Distinguish a missing factual input from an event or a judgement that needs specialist review.
- Check the assessment context. Consider the profile and assessment versions before relying on the result.
Review obligations and their sources
A source document tells you where a requirement comes from. An obligation record helps you work with that requirement in context: its conditions, its relationship to your firm and its links to controls or reporting.
The maintained framework includes Cyprus and EU regulatory material relevant to investment firms. Source references and available provenance help you return to the underlying material when a question needs closer examination.
- Read in context. Explore the obligation alongside its applicability outcome.
- Return to the source. Use regulatory references and available passages to inspect the basis.
- Connect the next step. Follow linked control and reporting requirements.
Timing, editions, conditions and jurisdiction can change the interpretation. A source match supports review; it does not settle every legal question.
Navigate controls and reporting
Operational requirements bring the regulatory framework closer to daily work. Review the activity, timing, responsible owner and expected evidence alongside the linked requirements.
The work queue brings eligible dated controls into focus. The broader library keeps reference material, event-driven requirements and unresolved scheduling items available for review.
- Controls. Understand what needs to be done and which requirements it supports.
- Reporting. Explore reporting requirements, timing and supporting operational work.
- Scheduling. Distinguish known dates from work that still depends on an event, an input or configuration.
Planning and execution are different. A listed control, a due date or a written policy does not by itself establish that a control operated effectively.
Retrieve OS records through your AI client
Instead of rebuilding the firm's regulatory context in each conversation, let a compatible AI client retrieve it from Compliance OS.
What it brings into the conversation
The connector provides access to structured company context, questionnaire requirements, obligations, controls and source references within the authorised company scope.
It also provides bounded checks for external-source research drafts. Those checks can support evidence review; they do not certify the final answer or a private-document assessment.
How you can work with it
- Ask your AI client to retrieve the relevant OS records, including every required page.
- Review those records alongside material available in your chosen AI environment.
- Ask for supported proposals, evidence references, contradictions and unresolved questions.
- Review the outcome and confirm any profile changes through the authorised OS workflow.
“Use my company context to explain which questions still need an answer, what evidence would help, and what I need to review.”
Example request · no AI request is sent from this page
Connector retrieval and evidence-checking capabilities are in pilot validation. Client compatibility, document access and model behaviour vary. The connector does not automatically save profile answers or submit audit findings.
Review documents in your chosen workspace
The connector workflow is designed around public regulatory sources and the structured company facts needed to assess applicability. It does not require private company documents to be uploaded to Compliance OS.
Review private material in your chosen AI environment. The AI can help propose answers with references, while confirmation remains with you. The document-access and data-handling settings of that environment still apply.
This is a way to reduce document collection while giving the regulatory work a consistent foundation.
Product questions
Is Compliance OS a KYC or screening tool?
Its focus is the wider compliance operating framework: company facts, applicability, obligations, controls and reporting. It is designed to support work beyond customer onboarding and screening.
Does each firm need a custom-trained AI model?
The connector approach supplies maintained context to a compatible AI client. It does not require a custom-trained model for each firm. The client still needs an authorised connection and appropriate access to the material you want it to review.
Does the AI decide whether my firm is compliant?
No. AI can help examine requirements and evidence, identify questions and propose answers. The professional reviews those proposals. Applicability, control design and evidence of actual operation remain distinct questions.
What happens when information is missing or out of date?
The gap remains visible. Unanswered facts, unverified information, stale calculations and unresolved judgements need different handling. A refreshed assessment should use the intended confirmed profile version.
Can I use any AI client?
Only compatible clients with the required connector support. Browsing, file access and document limits depend on that client. The pilot is being used to validate the actual workflows; universal compatibility is not assumed.
What the pilot will help evaluate
The pilot will help evaluate the profile-to-assessment workflow and the use of OS records in compatible AI clients. Participants can bring specific tasks and identify where records, explanations or workflows need improvement.