Insurance software your auditor can read.

For carriers, Assekuradeure, brokers and claims service providers: build portals, claims and underwriting workflows around your systems of record, with approvals, audit trail and one release for every brand you run.

Modernize workflows around your systems of record without breaking what is already live.

Where it runs

Nuclicore-managed on Azure (EU) or Hetzner (Germany), or your own cloud (BYOC). Single tenant on Enterprise.

Integrations

APIs, webhooks, event streams, batch and SFTP.

Governance

Preview, test, production, approvals, audit trail, redeploy any version.

Ownership

Exportable source code. Export to GitHub.

Multi-brand

One release on several branded domains with separate data.

Carrier-grade controls, built in

Insurance delivery is change control. Nuclicore is designed to ship faster without losing approvals, traceability, or ownership clarity.

Change control

Tasks with acceptance criteria, review points, and approval gates before promotion.

Traceability

Audit-ready visibility into what changed, when, and why across releases.

Environments

Preview, test, and production to validate changes before they touch live operations.

Redeploy

Every release stays in the history. A known-good version goes back to production in minutes.

Access and identity

RBAC and enterprise identity patterns aligned to regulated delivery expectations.

Ownership

Standard, portable code so your teams can review and operate without platform risk.

Documents and e-invoicing

PDF generation from templates, PDF merging, ZUGFeRD e-invoices. E-signature coming.

Multi-brand deployments

One release, served under each brand's domain with its own secrets, logos and database schema.

Built for every insurance delivery model

Align scope, workflow ownership, and governance for the exact segment you operate in.

Carriers

• Faster change delivery with governance
• Reduced rework with defined acceptance criteria
• Audit-ready traceability across releases

• FNOL and claims triage
• Underwriting referrals
• Policy servicing and endorsements

Start here: FNOL intake and triage, or an adjuster workbench workflow.

Assekuradeure and MGAs

• One portal, every brand you underwrite for
• Partner-ready workflows with clear controls
• Controlled releases per programme

• Bordereaux intake and validation
• Delegated underwriting rules
• Claims notifications and reconciliation

Start here: a customer or partner portal served under two brands from one release.

Brokers

• Better client experience and transparency
• Fewer manual handoffs
• Compliant document flows

• Quote/bind intake
• Endorsements servicing
• Secure document exchange and status tracking

Start here: secure document exchange and real-time status tracking for clients and carriers.

Claims and service providers

• Operational throughput across client programs
• Consistent processes for shared services
• Clear audit trails for reporting

• Intake and assignment
• Tasking and SLA tracking
• Evidence collection and reporting

Start here: intake and assignment with SLA tracking and reporting-ready audit trails.

Starter pilots that work in insurance

Pick one workflow, get it running with governance, then expand. This keeps scope predictable and security reviews focused.

Claims FNOL and Triage Pilot

Best for carriers and TPAs

Standardize intake, route work to the right team, and reduce manual handoffs with governed approvals.

• Working workflow in preview and test
• Approval checkpoints and audit trail
• Integration plan for systems of record

• Sample FNOL fields and routing rules
• Role model and approval needs
• Test environment or sandbox access

Assekuradeur portal and bordereaux pilot

Best for MGAs and delegated authority programs

Validate bordereaux files, reconcile submissions, and surface exceptions with traceability.

• Controlled ingestion and validation
• Exception queues with decisions logged
• Monitoring and reconciliation visibility
• Second brand as a deployment label

• Sample bordereaux files and validation rules
• Program structure and roles
• Target system or reporting destination

Broker Portal and Document Exchange Pilot

Best for brokers and carrier distribution teams

Give partners a secure portal for status, documents, and requests without exposing core systems.

• SSO-ready portal pattern
• Secure file handling and audit trails
• Clear status and handoff points

• Partner workflows and document types
• Identity requirements (SSO policy)
• Status and integration endpoints

In production at German insurers

What our insurance customers built, and how long it took.

Broker Collective Assekuradeur

Customer portal live in six weeks, served under two underwriting brands from one release. IAM, partner portal, claims and purchase flow builder followed.

Nürnberger Versicherung

LTA Reiseschutz

What you can build across claims, underwriting, and distribution

Deliver governed software around your systems of record, with review points, traceability, and code ownership.

Claims

FNOL Intake and Triage

Capture FNOL data, route to the right team, and standardize loss details before adjuster handoff.

portal forms, email/PDF intake, core claims API, vendor updates via webhooks.

triage decision, assigned task, structured claim record, audit trail entry.

• RBAC
• Audit log
• Preview/test/prod environments

Adjuster Workbench and Tasking

Coordinate adjuster assignments, reserves updates, and vendor touchpoints with a governed task workflow.

claims system API, vendor feeds, event streams, document management.

task queues, approvals, reserve update requests, decision logs.

• Approvals
• Redeploy
• Monitoring

Claims Document Processing and Payments

Ingest supporting evidence, validate documentation, and trigger payments with controlled checkpoints.

secure uploads, DMS, payments or accounting APIs, batch reconciliation.

validated evidence bundle, payout request, reconciliation record, audit trail entry.

• Secure file handling patterns
• Encryption at rest/in transit
• Audit log

Fraud and Exception Review

Route flagged claims to exception queues with traceable decisions and escalation paths.

rules engine inputs, analyst queues, notes and evidence attachments.

exception decisions, escalations, decision rationale, audit logs.

• RBAC
• Approvals
• Audit log

Underwriting and Policy

Underwriting Referrals and Rules

Escalate referral cases with underwriting notes, rule thresholds, and decision logs in one flow.

quoting inputs, PAS and underwriting APIs, broker submissions via web.

referral decision, required conditions, approvals, audit trail entry.

• Approvals
• Audit log
• Preview/test/prod environments

Policy Servicing and Endorsements

Manage endorsements, adjustments, and mid-term changes without disrupting policy admin systems.

PAS, billing, document generation, broker portal, batch updates via SFTP.

endorsement request, approval decision, issued documents, traceable change record.

• RBAC
• Redeploy
• Integrations via APIs/webhooks/SFTP/batch

Renewal and Mid-Term Adjustment Workflows

Coordinate renewal data, risk review, and update notices with clear approval checkpoints.

renewal data feeds, analytics inputs, document generation, outbound notifications.

renewal decisions, tasks, notices, audit trail of approvals and changes.

• Approvals
• Audit log
• Monitoring

Distribution and Partner Ecosystems

Broker and Partner Portals

Give brokers real-time status, document exchange, and controlled visibility into policy lifecycle steps.

SSO, broker submissions, document uploads, status updates via APIs/webhooks.

case status, required actions, issued documents, traceable interactions.

• SSO/SAML/SCIM
• RBAC
• Secure file handling patterns
• Multi-brand labels

Delegated Authority and Bordereaux Automation

Validate bordereaux files, reconcile submissions, and track delegated authority compliance.

SFTP/batch bordereaux, validation rules, reconciliation outputs to data warehouse.

validation reports, exceptions queues, reconciled records, audit-ready compliance trail.

• Audit log
• Monitoring

Fits your systems of record

Most ROI comes from removing manual handoffs and connecting to systems of record with clear ownership of every interface.

We do not replace your core platforms. We build governed workflows around them so policy admin, claims, billing, document management, CRM, and data warehouses stay authoritative.

We integrate through REST APIs, webhooks, event streams, SFTP, batch files, and middleware. If a system has no stable interface or no test environment, integration becomes a dedicated workstream. We surface those constraints in week 1 so delivery stays predictable.

What we need from you

• Interface spec or sample files (e.g., bordereaux format)
• Test environment or sandbox access
• Data fields, roles, and approval rules
• Security contacts and review timeline

Integration patterns supported

• REST APIs and webhooks for real-time workflows
• Event streams for system-of-record updates
• Batch files and SFTP for legacy feeds
• Middleware and data hubs for orchestration

Governed releases, stable production

Every change is traceable to an approved task and acceptance criteria. This supports audit, dispute defensibility, and predictable change control.

• Scope is clarified and acceptance criteria are defined before implementation.
• Work is delivered in reviewable increments via tasks.
• Releases move through preview, test, and production environments.
• Every change is approved by a named person; every completed task is one commit.
• Any earlier release can be redeployed.
• Audit logs capture key actions.

Security and data controls for regulated teams

Each application runs its own backend, with a managed, encrypted Postgres per environment. Enterprise labels get their own schema. Dedicated single-tenant infrastructure and BYOC on Enterprise, with encryption at rest and in transit.

RBAC, audit logs, and monitoring keep access controlled. Your workspace content is not used to train models, and deployment options (managed single tenant or BYOC) are available for Enterprise customers.

Security controls in practice

• Own backend per application, managed Postgres per environment with each application on its own table suffix, dedicated or single tenant databases on Enterprise.
• Encryption in rest and in transit
• RBAC, audit log, and monitoring
• No model training on your content, and workspace isolation
• DORA contract addendum, register of information data sheet and a documented exit

What a first insurance pilot looks like

We align on a focused workflow and deliver reviewable increments with clear governance.

Scope, acceptance criteria, architecture outline

Align on a single insurance workflow, define success criteria, and map the interfaces and governance needs.

Build the first workflow slice, preview review

Deliver a reviewable slice in preview with clear approvals and traceability for stakeholder input.

Integration and hardening, test environment

Connect to systems of record and validate data flows in test with monitoring and audit visibility.

Security gate, production release or controlled rollout

Security gate, sign-off, production release. Every release stays redeployable.

Success criteria examples

• Fewer manual handoffs in the chosen workflow
• Faster cycle time from request to release
• Audit-ready traceability for approvals and changes

Insurance FAQ

Answers tailored to regulated insurance delivery and integration realities.

Do you train models on our claims data or code?

No. Your workspace content, including your data and your code, is not used to train models. Customer workspaces are isolated from each other. Access is limited to what is needed to operate the service and support you.

We fall under DORA. Can we use Nuclicore?

Yes. In DORA terms Nuclicore is an ICT third-party service provider, and we support your obligations under Articles 28 to 30: a contract addendum with the Article 30 provisions, the data for your register of information including the subprocessor chain, audit and access rights, incident notification and a documented exit. The exit is practical, not theoretical: standard code, a standard database, and every release backed up into your own GitLab. If you are an intermediary that is not supervised under DORA directly, the same package answers the requirements your risk carriers pass down by contract. We do not call ourselves DORA-certified, because no such certification exists.

Can we deploy in our own cloud (BYOC) for data residency?

Yes. You can run in a Nuclicore-managed single-tenant environment or in your own AWS, Azure, or GCP account (BYOC), depending on your governance and residency requirements. In BYOC, your network controls, keys, and secrets stay in your cloud boundary.

How do you integrate with core systems and broker ecosystems?

We integrate using the interfaces you already have: REST APIs, webhooks, event streams, and, where needed, batch and SFTP. We align on the system of record, the ownership of each interface, and a test environment early so integration stays predictable.

How do you handle bordereaux and batch-based data exchanges?

We support batch pipelines and scheduled jobs with schema validation, idempotent processing, retries, and monitoring. For bordereaux, we start with your file formats and validation rules, then build a controlled ingestion and reconciliation workflow with audit logs.

What governance controls exist for approvals and audit trails?

Work is organised into reviewable tasks with acceptance criteria. Releases move through preview, test and production with approval gates, and any earlier release can be redeployed. Changes are traceable, and actions are captured in audit logs so teams can review what changed, when and why.

Who owns the code and can we export it to GitHub?

You own the code generated for your application. Nuclicore produces standard, portable code and supports exporting the full repository to your GitHub so your engineering team can review, extend, and operate it independently.

How do updates, bug fixes, and change requests work after launch?

You submit changes as new tasks, with scope and acceptance criteria reviewed before implementation. You review working software in preview, then promote through test to production with approvals. This keeps changes controlled and reduces the risk of breaking what is already live.

What does a first pilot look like for a carrier or MGA?

A typical pilot starts with one high-impact workflow, for example FNOL intake, claims triage, underwriting referrals, policy servicing, or bordereaux ingestion. Week 1 locks scope and acceptance criteria. Weeks 2–3 deliver reviewable increments and integration. Week 4 focuses on security review, hardening, and a controlled production rollout.

What security review artifacts can you provide?

We can provide an architecture overview and data flow, environment and deployment model details, access control and audit log behavior, and outputs from security scanning and remediation processes where applicable. We align early with your security team on required evidence and review steps, plus nightly ZAP scan reports and the automated dependency audit from each release.

How do you ensure changes do not break what is already live?

We separate preview, test and production environments and promote changes through them with approvals. The workflow is task-based and reviewable, and any earlier release can be redeployed. This reduces uncontrolled changes and keeps production stable while you iterate.

We run several brands. Do we need several applications?

No. Deployment labels serve one release under each brand's domain with separate secrets, logos and database schema. Broker Collective runs two underwriting agencies this way.

Turn insurance backlogs into running software.

Portals, claims and underwriting workflows with approvals, audit trail and code ownership. In production at German insurers.