For EU and international corporations

Octelligence for EU and international corporations.

EU data residency, GDPR-compliant processing, multi-currency, and the same universal corporate-records mechanics that work for any privately-held company. Deep statutory automation for 35 jurisdictions today; storage and universal mechanics for the rest.

Get started Talk to us about your jurisdiction
EU data hosted in the EEA. GDPR Article 28 processor.
What you get
EU data residency

Customer data stored in the EEA, default region Frankfurt. Alternative EU regions on Scale and Portfolio Licensing.

Universal mechanics

Share register, certificates, cap table, audit log. Work for any corporation, anywhere.

GDPR-compliant processing

Article 28 processor. DPA available. Sub-processors disclosed and updated.

Multi-currency cap tables

EUR, GBP, CHF, USD, CAD, and major regional currencies. Mixed-currency rounds supported.

What "international" means here

Two levels of support, clearly separated.

Most corporate-records platforms either claim universal coverage they cannot back, or only support a single jurisdiction. Neither is honest about what they actually do.

Octelligence supports corporations in any jurisdiction at the platform-mechanics level: share register, share certificates, cap table, resolutions, audit log, multi-currency, role-based access. These mechanics are the same whether the corporation is a Delaware C-corp, a German GmbH, a Dutch BV, a French SAS, or a Singapore Pte Ltd.

On top of those universal mechanics, deeper statutory automation, pre-built statute-specific templates, jurisdiction-specific filing calendars, conflict-of-interest workflows tied to local conflict rules, is available for 35 jurisdictions today. Outside those 14, the universal mechanics still work; the statute-specific automation is on a roadmap that follows customer demand.

Honest scope
  • 35 jurisdictions: deep statutory automation

    23 US states (including Delaware), federal CBCA and all 10 Canadian provinces, and the UK. Pre-built resolution templates with statute citations, jurisdiction-specific filing calendars, conflict-of-interest workflows.

  • EU member states: storage + universal mechanics

    Data hosted in the EEA. Cap table, share register, certificates, and resolutions all work. Statute-specific automation not yet built.

  • Rest of world: universal mechanics

    Singapore, UAE, Cayman, BVI, Switzerland, Australia, New Zealand, others. Storage region defaults to nearest available; universal mechanics work the same way.

  • Documents and records: tracked everywhere

    A French SAS’s registre de mouvements de titres can be stored, structured, and audited inside Octelligence today. The statute-specific French template is not pre-built; the underlying record is.

Coverage matrix

Three tiers of support, by region.

EU data residency is universal. Deep statutory automation is targeted at the 35 jurisdictions where current customers are concentrated. The matrix below is the honest answer.

  • Universal mechanics: every jurisdiction
  • EU data residency: every EU/EEA customer
  • Deep statutory automation: 35 jurisdictions today, more added as demand justifies
Region Storage Universal mechanics Deep automation
Canada (CBCA + 5 provinces) CA region ✓ ✓
US (8 states: DE, CA, NY, TX, FL, NV, WA, MA) US region ✓ ✓
United Kingdom EU / UK region ✓ ✓
EU member states (DE, FR, NL, IE, LU, others) EU region (EEA) ✓ Roadmap
Switzerland, EEA non-EU EU region (EEA) ✓ Roadmap
Singapore, Hong Kong, UAE, Cayman, BVI Nearest region ✓ Roadmap
Australia, New Zealand AU region ✓ Roadmap
Rest of world Nearest region ✓ On request

Universal mechanics: share register, share certificates with QR verification, cap table with SAFE/option/warrant modeling, board and shareholder resolutions, role-based access, audit log, multi-currency. Deep automation: pre-built statute-specific templates, conflict-of-interest workflows tied to local statute, jurisdiction-specific filing-deadline calendars.

EU compliance posture

GDPR, data residency, and the EU compliance stack.

Practical compliance, not just claims. EU customer data is processed under a GDPR Article 28 processor relationship; subject-access, portability, and deletion are supported; sub-processors are disclosed; data residency is configurable.

  • GDPR Article 28 processor; DPA available on request
  • EEA data residency by default for EU customers
  • Subject-access, data portability, and deletion supported
  • Sub-processors listed publicly and updated when changed
  • UBO register awareness under EU AMLD 4th/5th/6th Directive
Data Processing Agreement

Standard GDPR-compliant DPA available on request, terms aligned with EDPB guidance and EU Standard Contractual Clauses where transfers apply.

EU data residency

Default Frankfurt. Alternative EU regions on Scale and Portfolio Licensing. Backups and replicas remain inside the EEA.

Data subject rights

Access, rectification, portability, deletion, and restriction of processing supported. Self-serve for individuals; SLA-backed for controllers acting on behalf of subjects.

UBO register awareness

EU AMLD 4th/5th/6th Directive ultimate-beneficial-owner reporting. Records structured to support UBO disclosure where applicable.

See the security page, privacy policy, and sub-processors list for full detail.

Entity types recognized

Your entity type, recognized.

Octelligence labels share-issuing entities by their actual local form, not generically. Each form has a corresponding glossary entry covering structure, share types, governance, and the nearest US/UK equivalent.

GmbH (Germany)

Gesellschaft mit beschränkter Haftung. The German private limited company.

View glossary entry
Aktiengesellschaft / AG (Germany)

German stock corporation, public-company form. Roughly equivalent to a US C-corp or UK PLC.

View glossary entry
BV (Netherlands)

Besloten Vennootschap. The Dutch private limited company. Common holdco vehicle.

View glossary entry
SAS (France)

Société par Actions Simplifiée. The modern French startup vehicle.

View glossary entry
SE (Societas Europaea)

European Company. Pan-EU corporate form for cross-border operations.

View glossary entry
Pte Ltd (Singapore)

Private limited company under Singapore's Companies Act. Common international holdco vehicle.

View glossary entry
UBO register (EU AMLD)

Ultimate beneficial owner register under the EU's 4th, 5th, and 6th Anti-Money Laundering Directives.

View glossary entry
Handelsregister / commercial register

German commercial register and the equivalent registries across the EU.

View glossary entry
Common questions

Frequently asked

Yes, at the platform-mechanics level. The universal corporate-records mechanics (share register, share certificates, cap table, resolutions, audit log) work for any privately held corporation regardless of jurisdiction. EU customer data is stored on EU-region infrastructure with GDPR-compliant processing. Jurisdiction-specific statutory automation (preformatted resolutions, statute-specific templates, filing-deadline calendars) is currently available for 35 jurisdictions: federal Canadian (CBCA), ten Canadian provinces, 23 US states, and the United Kingdom. Other EU and international jurisdictions are supported for storage and universal mechanics today.

EU-region cloud infrastructure within the European Economic Area, configurable per customer. Default region is Frankfurt; alternative EU regions are available on the Scale and Portfolio Licensing tiers. Backups and replicas remain inside the EEA. The processing complies with GDPR Article 28 (processor) requirements; the data processing agreement is available on request.

Yes, for storage and universal corporate-records mechanics. The share register, share certificate, audit log, and cap table all work for a GmbH or SAS the same way they work for a Delaware C-corp. What is not yet automated for these entities is deep statutory automation, for example GmbHG-specific shareholder meeting requirements or French Code de commerce auditor-appointment forms. Those remain documentable manually inside the platform but do not yet have prebuilt jurisdiction-specific workflows.

Yes. EU customer data is stored in the EEA, processed under a GDPR-compliant Data Processing Agreement, subject to the customer's instructions as controller. Subject-access requests, data portability, and deletion requests are supported. Sub-processors are listed and updated on the subprocessors page. The Privacy Policy details the lawful bases for processing.

Where customer demand justifies the engineering investment, yes. The 35 currently supported jurisdictions reflect where existing customers are incorporated. New jurisdictions are added when there is enough buyer pull to justify building the statute-specific templates and automation. EU customers can talk to us about their specific jurisdiction and timing.
International customers
EU data residency. Universal mechanics. Honest scope.

Talk to us about your jurisdiction. We will tell you exactly what works today and what is on the roadmap.

Get started Talk to us