Virtualisation
Workload consolidation and logical separation.
Infrastructure
Infrastructure, servers and datacenter services
We design and manage infrastructure for business applications and systems: servers, virtualisation, backup and connectivity. Where the architecture requires it, we use our own IPv4 and IPv6 resources and operate our own ASN.
INFRASTRUCTURE STACK
The server is only one layer of the infrastructure.
Application availability depends on connectivity, network, firewall, virtualisation, server, storage, backup and monitoring. We treat these as a system rather than isolated products.
NETWORK IDENTITYIPv4 + IPv6 · own ASN
One Core Spark operates its own IPv4 and IPv6 resources and its own ASN, used where the service architecture requires them.
ARCHITECTURE
From the Internet layer to monitoring.
Each project may use only part of this stack, but the dependencies between layers still matter.
INTERNET→NETWORK→FIREWALL→VIRTUALISATION→SERVER→BACKUP→MONITORING
CAPABILITIES
Infrastructure that can be operated, not only installed.
Managed servers
Operating system, updates, services, monitoring and interventions.
Backup & recovery
Backup policies aligned with data criticality and recovery objectives.
IPv4 / IPv6
Connectivity and addressing using our own resources where needed.
Monitoring
Visibility into services and indicators relevant to incident detection.
Migration
Dependencies, change window, backup and rollback plan.
OSmanaged
UPDATESplanned
SERVICESmonitored
BACKUPverified
ACCESScontrolled
SERVER MANAGEMENT
Infrastructure continues after installation.
Administration can cover updates, services, access, backup, monitoring and interventions, with clear boundaries between One Core Spark, the client and third-party providers.
Moving infrastructure needs a rollback plan.
We inventory dependencies, define maintenance windows, prepare backups and validate services after the move.
Backup is not the same as recovery.
The strategy should reflect what data is critical, how much loss is acceptable and how quickly operations need to resume.
FAQ
Questions before the first technical discussion.
These answers are general. Responsibilities and service levels are defined in the actual proposal or agreement.
What does the datacenter and infrastructure service cover?+
Depending on the project: servers, virtualisation, administration, backup, monitoring, connectivity, migration and integration with the company network.
Do you use your own IPv4 and IPv6 resources?+
Yes. One Core Spark operates its own IPv4 and IPv6 resources and its own ASN, used where the service architecture requires them.
Do you manage servers after deployment?+
Yes. Administration can cover the operating system, virtualisation, updates, monitoring, backup and interventions according to the agreed responsibility model.
Can you migrate existing infrastructure?+
Yes. Migration starts with dependencies, maintenance windows, backups and a rollback plan, then proceeds in controlled stages.
NEXT STEP
Request a discussionTell us the technical context.
We can start with a specific issue, an audit or a discussion about the responsibilities you want to outsource.