Constraints and boundaries
Quality depends on source content, access labels and an evaluation set; the model does not replace the process owner.
VIRTEK · ARCHITECTURE LIBRARY
Not articles or marketing diagrams, but engineering patterns with boundaries, components, scale, recovery targets, controls, constraints and technology-stack options.
Find the closest target pattern22 baseline patterns · 24 service areas · fit validated in the labRTO/RPO and scale values are orientation points. They must not enter a specification until business criticality, dependencies, connectivity, licensing and operating procedures have been validated.
ENGINEERING CATALOGUE
Filters identify a useful starting point. The final design follows workload, data, integration and availability assessment.
Local and external models behind one gateway, grounded enterprise retrieval, quality evaluation and controlled data access.
From one department to a multi-tenant enterprise platform
Quality depends on source content, access labels and an evaluation set; the model does not replace the process owner.
Tenant isolation, ACL-aware retrieval, DLP, prompt protection, data masking, audit trails and human approval for critical actions.
Open-weight LLMs, vLLM/llama.cpp, PostgreSQL with pgvector and OpenSearch; sovereign models and platforms where required.
Compare models, chunking, retrieval coverage, answer quality, context leakage and performance on a representative corpus.
Orchestration for agents, tools and business systems with authority control, tracing, evaluation and safe action execution.
From one workflow to an enterprise agent catalogue
Autonomy is bounded by error impact; financial, HR and operational actions require approval gates.
Short-lived authority, tool allowlists, secrets outside context, argument validation, decision audit and emergency stop.
Open orchestrators, MCP-compatible gateways, Kafka/RabbitMQ/NATS queues and local models to avoid single-cloud lock-in.
Test tool failure, invalid arguments, human escalation, cost limits and result reproducibility.
Compute clustering, load balancing, resilient databases, distributed storage and observability without a single point of failure.
From three nodes at one site to a dual-data-centre design
A cluster does not replace backup; inter-site latency and application behaviour determine the viable topology.
Role segmentation, MFA for administration, encryption, hardening, bastion access and isolated management planes.
Proxmox VE, OpenStack or sovereign virtualisation; PostgreSQL/Patroni and alternative databases and storage where certified.
Validate node, network, disk and site failure, quorum, split-brain, failover time, degraded operation and restore from backup.
Three copies, two storage platforms, off-site and immutable copies, automated recovery verification and an isolated recovery zone.
From tens of VMs to multi-site estates and petabyte archives
Copy count does not guarantee recovery: ownership, regular tests, dependency mapping and separate credentials are required.
Immutability, air gap, separate management identity, MFA, dual control, deletion monitoring and malware scanning on recovery.
Veeam or compatible platforms, Bacula/UrBackup, S3 Object Lock, tape libraries and sovereign backup suites.
Recover a complete service chain and validate RTO/RPO, immutability, clean backups, runbooks and operation without the primary identity domain.
Managed WAN links, resilience, segmentation, identity and device posture checks, unified policy and observability.
From three to hundreds of branches, offices and remote users
Quality depends on local carriers, latency-sensitive applications and an accurate map of flows between segments.
Continuous identity and posture checks, least privilege, microsegmentation, policy-based TLS inspection and central logging.
OpenWrt/VyOS/FRR, WireGuard/OpenVPN, sovereign NGFW/NAC and independent DNS and monitoring options.
Emulate link loss, degradation, rerouting, compromised posture, IAM failure and access to critical applications.
Pooled compute, network and storage with self-service, quotas, infrastructure as code and external cloud integration.
From 3–6 nodes to multiple availability zones
Economics depend on utilisation, operating skills, licensing and image standardisation; small estates may not justify complex orchestration.
Tenant separation, isolated management, MFA, secrets management, signed images, policy as code and continuous inventory.
OpenStack, Proxmox VE, Kubernetes, Ceph, OpenTofu/Ansible and sovereign cloud or virtualisation platforms.
Validate node and storage failure, IaC deployment, scaling, quotas, tenant isolation and workload portability.
Personal and pooled desktops, applications and data in a controlled environment with MFA and endpoint management.
From 50 to several thousand concurrent sessions
Workload, peripherals, multimedia and latency must be measured; licensing and GPU can dominate cost.
MFA, role-based data egress, clipboard and USB controls, segmentation, EDR and privileged session recording.
KVM/Proxmox, sovereign VDI and operating systems, Apache Guacamole for selected use cases and open profile services.
Measure login and UX under loss, peripheral, GPU and printing compatibility, density and profile recovery.
Registry, approval workflows, signatures, tasks, counterparty exchange, versions and long-term archival storage.
From one department to a group-wide document registry
Legal validity depends on signature type, document format, EDI operator and policy; a PDF is not a structured statutory document.
Role and object access, immutable originals, signer MFA, certificate validation, malware scanning, legal hold and full audit.
Nextcloud, PostgreSQL/OpenSearch, sovereign DMS/EDI, approved signature providers and open BPM engines.
Run a contract and statutory document end-to-end: versions, parallel approval, rejection, signing, receipts, search, archive package and recovery.
FROM PATTERN TO PROJECT
Use a selected pattern as the foundation for a technical specification, RFP questionnaire, PoC or engineering assessment.