Architecture and responsibilities
Document sites, boundaries, application environments and the division of responsibility.
Infrastructure and application operations
Keep control of your infrastructure without carrying the operational burden alone.
April Computers operates the infrastructure and application foundations behind managed company services, business applications and integrated AI.
Use infrastructure operated by April Computers, infrastructure controlled by your organization or a combination of sites. We coordinate responsibilities, backup and recovery around the environment you need.
More than infrastructure capacity
Infrastructure only becomes a dependable service when responsibilities are clear.
Choosing compute, storage and networking is only the beginning. The environment must also be supervised, maintained, protected and prepared for recovery.
April Computers works with your organization to define who controls the infrastructure, who performs each operational task and how the application layer is managed over time.
Supervision and follow-up
Supervise the agreed environment and respond when operational attention is required.
Maintenance and capacity
Coordinate infrastructure maintenance, application lifecycle and capacity requirements.
Backup and recovery
Protect managed sites daily and define how data and services will be restored.
Three operating models
Use our infrastructure, yours or a combination of sites.
April Computers-operated
One provider for both layers
Run managed services and agreed applications on infrastructure operated by April Computers.
- Do not own the underlying infrastructure
- One relationship for infrastructure and applications
- Begin without building a private site
Customer-controlled
Retain ownership and location control
Run applications on suitable infrastructure owned, selected or controlled by your organization.
- Use appropriate existing infrastructure
- Keep systems at a selected location
- Delegate agreed operational work
Multiple sites
Give each location a defined role
Combine locations, such as an active environment at one site and recovery preparation at another.
Multiple sites do not by themselves create high availability. The recovery model must be explicitly designed.
Assess before replacing
Start with the infrastructure you already have.
A controlled environment does not always require replacing everything or beginning with a large infrastructure investment.
April Computers can review existing compute, storage, networking, connectivity and site constraints to identify what can be retained, what must change and whether the environment is suitable.
Existing infrastructure is assessed before it is accepted into a managed service. We do not assume that every existing system is automatically suitable.
Assess suitability
Review capacity, connectivity, storage, maintainability and recovery needs.
Define the target architecture
Clarify Kubernetes, persistent data, connectivity, backup and supervision.
Improve progressively
Add capacity according to service needs rather than replacing everything at once.
Establish operational discipline
Bring supervision, maintenance, backup and recovery into one model.
Two coordinated layers
Keep infrastructure and application responsibilities distinct but connected.
Clear boundaries make it easier to understand what April Computers operates and what remains under customer control.
Infrastructure operations
The foundation beneath the applications
- Site and infrastructure configuration
- Compute, storage and private-network foundations
- Kubernetes infrastructure
- Supervision, capacity and maintenance
- Backup infrastructure and recovery preparation
Application operations
Coordinated through April Site Operator
- Application catalogues and customer environments
- Versions and capacity profiles
- GitOps configuration through Argo CD
- Active and recovery-site assignments
- Persistent data and recovery activation
April Site Operator manages the Kubernetes application layer. It does not remove the need for an agreed infrastructure model beneath it.
Baseline protection
Protect every managed site with a daily backup cycle.
Each managed site is protected by daily backups intended to support restoration after deletion, corruption or an operational incident.
Backup is not the same as a continuously running secondary environment. The restoration point depends on the latest successful cycle and the data covered by the agreed service.
Backup scope, retention and restoration procedures are defined for the managed environment. Application-specific requirements can be discussed during service design.
Backup is the baseline
Daily cycle
Protection follows the latest successful backup cycle.
Defined scope
Covered data and retention are agreed for the environment.
Restoration support
Procedures support recovery from operational incidents.
Prepared for site loss
Optional disaster recovery at a separate site.
Application data is transferred daily and restored on a recovery site. Persistent data, application versions and capacity profiles are maintained to prepare services for activation.
If the active site is lost, April Computers can activate the services, validate the environment and update managed gateways to redirect traffic.
Prepared through April Site Operator
Site assignments, intended configuration, versions, capacity profiles and persistent application data.
Clear recovery boundaries
An operated recovery process, not automatic failover.
- No active-active high availability
- No continuous replication
- No promise of zero data loss or zero downtime
- No automatic failover
The recovery site reflects the latest successful daily cycle, so up to 24 hours of recent changes may be lost.
Recovery time varies with the environment, site condition and validation required during activation.
Application-specific recovery
Define recovery according to the system.
The standardized separate-site model supports application environments operated through April Site Operator.
Other infrastructure, legacy systems or business applications may require a different recovery design. Their backup method, recovery point and recovery time must be assessed and defined separately.
This avoids presenting every workload as if it had the same architecture or recovery characteristics.
Control without isolation
Sovereignty through operational choice.
Retain meaningful choices about where systems run, who owns them and who performs the operational work.
Ownership
Use April Computers infrastructure or retain infrastructure ownership.
Location
Choose sites for active services, backups and recovery.
Technology
Use transparent foundations and selected open-source applications.
Operations
Choose complete operation or an agreed shared-responsibility model.
Sovereignty does not require operating everything alone. It requires knowing which choices remain available and which responsibilities have been delegated.
Designed to remain understandable
Durable operations with maintenance and recovery in mind.
Clear architecture
Keep site roles, environments and responsibilities documented.
Progressive capacity
Grow according to actual service and recovery requirements.
Repair and maintenance
Plan for updates, replacement and intervention over time.
Recovery discipline
Treat backup and recovery as recurring operational work.
Define the operating model
Move from infrastructure choices to clear responsibilities.
01
Review
Identify sites, infrastructure, applications, data, connectivity and responsibilities.
02
Define the boundary
Agree on ownership, operations, supervision, maintenance, backup and recovery.
03
Prepare
Complete changes, deploy the foundation and validate backup and access.
04
Operate and review
Run the environment and revisit capacity and recovery as needs evolve.
Define an infrastructure model your organization can control and operate over time.
Discuss your existing infrastructure, preferred locations, managed services and recovery requirements with April Computers.