ZTABS deploys self-hosted AI infrastructure for Amsterdam enterprises across DNB/AFM-supervised financial institutions, healthcare organisations, logistics companies and technology firms. Self-hosted deployment runs open-weight language models on customer-controlled hardware. Whether data remains within the organisation's security boundary depends on the actual configured full-stack data paths; on-premises hardware alone does not inherently guarantee zero external transmission.
Amsterdam self-hosted AI demand spans financial services (compliance automation, credit analysis, insurance processing), healthcare (clinical documentation, research analytics), logistics (route optimisation support, document processing, supply chain analytics) and technology (AI product development, data analytics). ZTABS is remote-first by design, with an office in Houston, Texas. Our self-hosted AI deployment services cover infrastructure deployment across markets.
Deployment scenarios and requirements
| Need | What we build | Key requirement |
|---|
| Financial services | Compliance AI, credit analysis, insurance processing | DNB/AFM supervision, GDPR, EU AI Act, DORA |
| Healthcare | Clinical NLP, research analytics, patient tools | GDPR, applicable health legislation |
| Logistics | Route optimisation support, document processing | Operational requirements, GDPR |
| Technology | AI product development, data analytics | GDPR, EU AI Act where applicable |
What self-hosted means
Self-hosted deployment runs open-weight language models on hardware the organisation controls. Self-hosting addresses scenarios where cloud AI APIs are contractually prohibited, where data classification requires controlled infrastructure, or where organisational policy favours infrastructure the customer controls.
What self-hosting does not automatically provide. On-premises hardware does not inherently guarantee GDPR compliance, EU AI Act compliance or zero vendor risk. GDPR applies based on controller and processor activities, not server location. The EU AI Act regulates based on risk classification, not deployment location. Self-hosted deployment supports compliance but is not a substitute for comprehensive compliance programmes.
EU AI Act phased implementation. The EU AI Act (Regulation 2024/1689 as amended by Regulation 2026/1744) entered into force August 2024. Prohibited practices from February 2025. General-purpose AI model obligations from August 2025. Annex III listed high-risk systems from 2 December 2027; regulated-product high-risk under Annex I from 2 August 2028. Article 50 transparency and Article 73 serious incident reporting apply based on classification and intended purpose.
Dutch works council rights. WOR Article 27 gives works councils consent rights over arrangements for monitoring employee work performance and presence, and over arrangements regarding the processing of and protection of employee personal information. AI systems with monitoring capability or that process employee personal information may require works council consent. Engagement before deployment is required where applicable.
Model licences. Open-weight models have specific licence terms. Llama 3 uses Meta's custom Community License. Open-weight means trained weights available for download; it does not mean open-source or full training-corpus disclosure.
Planning self-hosted AI for your Amsterdam organisation?
Tell us about your infrastructure, security requirements and use cases. We start with environment assessment and workload analysis.
Financial services deployment
Amsterdam's financial institutions supervised by DNB and AFM create demand for self-hosted AI supporting compliance, credit analysis and insurance operations.
DNB/AFM supervision. DNB supervises banks, insurers and pension funds for prudential requirements. AFM supervises conduct of business requirements. Both supervisors have expectations for technology governance, outsourcing and risk management. Self-hosted deployment supports governance and auditability for supervised entities.
DORA compliance. The Digital Operational Resilience Act applies from January 2025. DORA Article 29 establishes requirements for preliminary assessment of ICT concentration risk at entity level for arrangements supporting critical or important functions, assessing actual supplier and function dependence. Whether a particular AI deployment supports a critical-important function depends on the financial entity's own assessment. Self-hosted deployment reduces certain third-party dependencies but does not eliminate all DORA obligations.
Credit analysis. Self-hosted language models support credit assessment within the institution's infrastructure. EU AI Act Annex III includes creditworthiness assessment of natural persons as high-risk, except for systems used for fraud detection. Credit decisions require qualified credit personnel.
Insurance processing. Self-hosted AI supports claims analysis, underwriting document processing and policy administration. EU AI Act Annex III specifically identifies AI systems used for risk assessment and pricing in life and health insurance of natural persons. Insurance for natural persons has distinct AI Act classification from commercial and property insurance. Claims determinations require qualified personnel.
Compliance automation. Self-hosted AI supports AML/CFT compliance within the institution's infrastructure. The Dutch Anti-Money Laundering and Anti-Terrorist Financing Act (Wwft) applies. AI provides analytical support; reporting decisions require authorised compliance personnel.
Healthcare deployment
Amsterdam's healthcare organisations create demand for self-hosted AI supporting clinical documentation and research.
Healthcare regulation. Dutch healthcare data processing must comply with GDPR and applicable sector legislation. EU MDR applies to software qualifying as a medical device based on intended medical purpose. Engineering validation is distinct from clinical authority.
Clinical documentation. Self-hosted language models support Dutch and English clinical documentation, coding assistance and research analytics. Clinical decisions require qualified healthcare professionals. Dutch medical terminology processing requires evaluation against the engagement's clinical data.
Research analytics. Self-hosted AI supports analysis of research datasets. Academic medical centres and research institutions may process sensitive datasets under research ethics approvals. GDPR Article 89 research exemptions have specific conditions including appropriate safeguards.
Logistics deployment
Amsterdam's logistics sector creates demand for self-hosted AI supporting supply chain operations and document processing.
Route and supply chain analytics. Self-hosted AI supports supply chain analytics, demand forecasting assistance and logistics document processing within the operator's infrastructure. Operational decisions require qualified logistics personnel.
Customs and trade documentation. Self-hosted AI supports processing of customs declarations, trade compliance documents, shipping documentation and cargo manifests. Customs determinations require qualified customs and trade compliance personnel. AI provides document extraction and analytical support for processing the volume and variety of trade documentation flowing through Amsterdam's logistics infrastructure. Export control screening, sanctioned party checks and trade compliance reviews require authorised personnel; AI supports the screening process but compliance determinations remain human decisions.
Port and warehouse operations. Amsterdam's port and logistics infrastructure generates demand for AI-assisted operations. Self-hosted deployment supports processing of operational data within controlled environments where commercial sensitivity or contractual requirements restrict cloud processing.
Technology sector deployment
Amsterdam's technology companies create demand for self-hosted AI supporting product development, data analytics and platform operations.
AI product development. Self-hosted infrastructure supports technology companies developing AI-powered products where they need to control the full inference stack, maintain proprietary model configurations or avoid cloud API dependencies. Amsterdam's technology sector includes companies building SaaS platforms, fintech applications, marketplace platforms and enterprise software. Self-hosted deployment protects proprietary model configurations and training approaches.
Data analytics. Self-hosted language models support analysis of large datasets within the company's infrastructure. For companies processing personal data, GDPR obligations apply regardless of deployment model. Data science teams benefit from controlled infrastructure where they can experiment with model configurations, fine-tuning approaches and prompt engineering without cloud API rate limits. On-premises hardware alone does not inherently guarantee zero external data transmission; the full stack must be verified.
Platform operations. Self-hosted AI supports content moderation, user communication analysis, fraud detection and operational automation for platform businesses. Content moderation involves obligations under the Digital Services Act alongside GDPR and EU AI Act transparency requirements. Moderation decisions and user-affecting determinations remain with authorised personnel within the platform's governance framework.
Full-stack data path mapping
Self-hosted deployment requires mapping every component that processes data. The full stack includes the inference engine, tokeniser, embedding model, vector database, key-value cache, authentication layer, telemetry pipeline, backup systems, administrative interfaces, support channels, model update paths, tool-calling endpoints and RAG data sources. Each component has its own data flow and potential egress path. Data access propagates through retrieval results, cached responses, trace logs, exported analytics and adapters; this requires active management at each layer.
Supply chain and update management
Approved supply chain. Model weights and dependencies follow approved procurement with provenance review. Hash verification and scans reduce risk but cannot prove the whole stack is uncompromised. Staging with evaluation and rollback capability precede production deployment.
Illustrative Example
Example deployment: Amsterdam financial institution self-hosted compliance AI
An Amsterdam-based DNB-supervised bank needs self-hosted AI to support AML/CFT compliance screening, credit document analysis and DORA-compliant operations within its controlled infrastructure.
The deployment would install open-weight language models on GPU infrastructure within the bank's environment. AI models would process transaction monitoring alerts, extract structured data from customer documentation and support compliance analysts. Credit analysis models would process Dutch, English and other European-language financial statements.
Assumptions: the bank's infrastructure team manages the environment, existing compliance systems remain operational alongside the AI enhancement, works council engagement under WOR 27 is completed where applicable, EU AI Act high-risk classification for creditworthiness AI is addressed, DORA ICT risk management incorporates the AI system, all credit decisions remain with authorised officers, and all compliance reporting decisions remain with authorised personnel.
Residual risks include model accuracy variation across European language document types, works council consent timeline, EU AI Act compliance documentation requirements, GDPR deletion limitations for trained models, DORA ongoing obligations, GPU capacity planning and operational knowledge transfer. No guarantee of specific false positive reduction, processing speed improvement or compliance outcome.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Cost drivers for self-hosted AI
Self-hosted AI deployment has no published cost guide on this site. Cost varies significantly across engagements.
Model and workload factors. Model size, context requirements, KV cache, precision, batching and concurrency.
Infrastructure factors. GPU procurement, redundancy, power, cooling, network configuration and disaster recovery.
Regulatory factors. DNB/AFM documentation, GDPR compliance, EU AI Act documentation for applicable categories, works council engagement, DORA ICT risk documentation where applicable.
Integration factors. Connection to banking, compliance, clinical and logistics systems. Each integration's API access and data entitlements must be confirmed.
Operations and handover factors. Documentation, monitoring, model update procedures, capacity planning and knowledge transfer.
Need to scope self-hosted AI for your Amsterdam organisation?
Share your environment, security requirements and use cases. We provide a deployment assessment covering infrastructure, compliance and operational scope.
Proposal evaluation criteria
- Relevant self-hosted AI deployment experience across financial services, healthcare or logistics environments with supporting evidence
- Full-stack infrastructure design including data flow mapping, security architecture and regulatory documentation
- Integration plan covering actual API access, licence entitlements and data permissions
- Delivery milestones with measurable acceptance criteria including works council timeline where applicable
- Operations ownership covering model updates, patching, rollback and monitoring
- Provider team identifies who delivers engineering, trains users, delivers documentation and provides support; customer team identifies who provides environment access, validates domain-specific outputs (compliance accuracy, credit analysis quality, Dutch clinical NLP), accepts milestones and handles post-handover operations; both parties agree staff and user languages, documentation ownership and scope, translation responsibilities and handover materials
How delivery works
ZTABS is remote-first by design, with an office in Houston, Texas. CET/CEST timezone coordination for Amsterdam clients; scheduling and staff language commitments are agreed per engagement.
Environment assessment. Infrastructure review, security boundary analysis, integration targets and workload benchmarking.
Model selection. Candidate models evaluated against domain-specific test sets including Dutch and English capabilities.
Security and regulatory readiness. Applicable controls implemented. EU AI Act, GDPR and works council documentation prepared where applicable.
Pilot and acceptance. Pilot targets a single use case. Rollout extends with rollback capability.
Training and handover. User training, operations transfer and complete documentation.
When ZTABS is not the right fit
- Turnkey GPU hardware procurement for this engagement. We design requirements; procurement follows the organisation's channels.
- Qualified compliance officer, credit analyst, clinical authority or works council negotiator for this engagement. These require authorised personnel.
- Ongoing managed hosting for this engagement. Internal operations post-handover; retainers separately agreed.
- DNB/AFM licence application or regulatory representation for this engagement. Regulatory representation requires separate qualification.
- On-site embedded team for this engagement. ZTABS is remote-first by design. On-site separately agreed.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Amsterdam enterprises can commission white-label self-hosted AI platforms for distribution.
Data governance
Each engagement agrees data classification, processing boundaries and retention requirements. GDPR obligations apply. Data access propagates through retrieval results, cached responses, trace logs, exports and adapters; this requires active management at each layer. Training or fine-tuning on customer data requires documented authorised purpose, training-data scope, custodian approval and purpose limitations. Revocation is agreed and verified across active retrieval paths, vector stores, caches, exports, logs, backups and adapters as applicable; propagation lag is disclosed and affected access restricted while propagation is incomplete. Lawful retention, legal holds and regulatory preservation obligations are distinguished from active retrieval and use. Model weights may retain residual statistical patterns not individually reversible through source deletion; the engagement does not promise instant erasure of every backup or model weight. Residual-risk acceptance documents technical limitations but does not waive statutory rights or legal obligations. Separate legal review addresses GDPR data-subject rights, regulatory retention and applicable remedies.
Monitoring and operations
Infrastructure monitoring. GPU utilisation, memory, latency, throughput, storage and network health.
Security monitoring. Access logs, authentication events, anomaly detection.
Model quality. Evaluated against held-out test sets with domain-specific criteria including Dutch language performance and EU AI Act monitoring for applicable categories. Drift detection and periodic re-evaluation. Monitoring reduces risk but cannot guarantee all regressions are caught.
Capacity management. GPU utilisation trends inform capacity planning.
Handover
Deployment handover includes infrastructure runbooks, model configuration documentation, security and regulatory compliance documentation including EU AI Act documentation where applicable, monitoring dashboards, model update procedures, capacity planning guidance and escalation contacts. Post-handover support terms agreed per engagement.
Ready to deploy self-hosted AI in Amsterdam?
Share your infrastructure, security requirements and use cases. We start with environment assessment and workload analysis.