Defined scope
Objectives, responsibilities, assumptions, and boundaries aligned before execution.
Diagnostic → Project → Operations → Evolution
IT Projects with MaaS® Architecture
We plan and implement infrastructure, cloud, and security improvements with a defined scope, documentation, and result validation.
Clear engagement
From a technical problem to a verifiable delivery
Each project starts with a concrete need and moves forward with documented responsibilities, decisions, and acceptance criteria.
Business priorities
Technical decisions ordered by risk, operational impact, and company context.
Change control
Planned implementation with change records and a rollback plan when relevant.
Technical documentation
Architecture, configurations, inventories, or procedures produced for the project.
Delivery validation
Evidence and acceptance criteria defined to confirm the contracted outcome.
Organized transition
Knowledge transfer and a structured handoff to the team or contracted operation.
Project catalog
Ten paths to evolve IT
Engage a one-off initiative or build a phased journey. Each project highlights its primary MaaS® layer and may involve other layers according to environment dependencies.
01Secure and Governed Microsoft 365
Accounts, email, and documents without consistent controls.
Shielding & IdentityView scope and deliverables
01
Secure and Governed Microsoft 365
Accounts, email, and documents without consistent controls.
Best suited for
Companies using Microsoft 365 that need to organize identities, permissions, and collaboration protection.
Possible deliverables
- Tenant review
- MFA and access policies subject to licensing
- Email protection
- Permission review
- Joiner and leaver procedures
The final composition is defined in the diagnostic and technical proposal.
Discuss this project02Secure and Organized Google Workspace
Unprotected accounts, uncontrolled sharing, and scattered files.
Shielding & IdentityView scope and deliverables
02
Secure and Organized Google Workspace
Unprotected accounts, uncontrolled sharing, and scattered files.
Best suited for
Organizations that need to standardize administration, access, and information lifecycle in Google Workspace.
Possible deliverables
- Administrative review
- MFA
- Shared drives
- Permissions and sharing rules
- Retention subject to licensing
The final composition is defined in the diagnostic and technical proposal.
Discuss this project03Backup and Disaster Recovery
Backups without a strategy or unproven recovery.
Business ContinuityView scope and deliverables
03
Backup and Disaster Recovery
Backups without a strategy or unproven recovery.
Best suited for
Environments where downtime or data loss requires clear recovery objectives and procedures.
Possible deliverables
- Workload assessment
- Recovery objectives
- Solution design and configuration
- Restore tests
- Documented procedures
The final composition is defined in the diagnostic and technical proposal.
Discuss this project04Intelligent Infrastructure Monitoring
Failures discovered only after they affect operations.
Orchestration & GovernanceView scope and deliverables
04
Intelligent Infrastructure Monitoring
Failures discovered only after they affect operations.
Best suited for
Companies that need visibility into infrastructure and critical services.
Possible deliverables
- Monitoring with relevant technologies such as Zabbix
- Grafana dashboards when applicable
- Alerts
- Documentation
- Knowledge transfer
The final composition is defined in the diagnostic and technical proposal.
Discuss this project05Cloud Cost Optimization — FinOps
Cloud consumption without visibility and poorly sized resources.
Orchestration & GovernanceView scope and deliverables
05
Cloud Cost Optimization — FinOps
Cloud consumption without visibility and poorly sized resources.
Best suited for
Cloud operations that need to understand cost, capacity, and consumption ownership.
Possible deliverables
- Cost analysis
- Idle resource identification
- Sizing recommendations
- Commitment evaluation
- Budget controls
The final composition is defined in the diagnostic and technical proposal.
Discuss this project06Server Modernization and Cloud Migration
Aging infrastructure, insufficient capacity, or difficulty scaling.
Structural FoundationView scope and deliverables
06
Server Modernization and Cloud Migration
Aging infrastructure, insufficient capacity, or difficulty scaling.
Best suited for
Environments that need to renew servers or virtualization, or adopt cloud with controlled risk.
Possible deliverables
- Dependency assessment
- Solution architecture
- Pilot when applicable
- Migration and validation
- Rollback plan
The final composition is defined in the diagnostic and technical proposal.
Discuss this project07Secure Corporate Network and Site Connectivity
Unstable connectivity and lack of segmentation and control.
Structural FoundationView scope and deliverables
07
Secure Corporate Network and Site Connectivity
Unstable connectivity and lack of segmentation and control.
Best suited for
Companies with offices, branches, hybrid work, or distributed services.
Possible deliverables
- Network design
- Firewall and segmentation
- Corporate Wi-Fi
- VPN
- Site or cloud integration according to scope
The final composition is defined in the diagnostic and technical proposal.
Discuss this project08Endpoint Protection and Device Management
Computers without centralized protection and administration.
Shielding & IdentityView scope and deliverables
08
Endpoint Protection and Device Management
Computers without centralized protection and administration.
Best suited for
Teams that need standardized security, configuration, and updates for corporate devices.
Possible deliverables
- Endpoint protection
- Device policies
- Encryption
- Update management
- Pilot and operating procedures
The final composition is defined in the diagnostic and technical proposal.
Discuss this project09Data Governance and Information Security
No criteria for access, sharing, and retention.
Orchestration & GovernanceView scope and deliverables
09
Data Governance and Information Security
No criteria for access, sharing, and retention.
Best suited for
Organizations that need to understand their repositories and apply rules proportional to the information handled.
Possible deliverables
- Assessment of contracted repositories
- Information classification
- Access matrix
- Policies and retention
- Protection controls and user guidance
The final composition is defined in the diagnostic and technical proposal.
Discuss this project10Vulnerability Assessment and Penetration Testing
Unknown or unvalidated technical exposure.
Shielding & IdentityView scope and deliverables
10
Vulnerability Assessment and Penetration Testing
Unknown or unvalidated technical exposure.
Best suited for
Environments that need to identify vulnerabilities or validate exploitability through authorized testing.
Possible deliverables
- Formal scope and authorization
- Automated assessment and technical analysis or penetration testing, as contracted
- Evidence and risk classification
- Recommendations
- Retest when included
A vulnerability assessment identifies and analyzes exposure. Penetration testing adds controlled manual exploitation within the authorized scope; an automated scan is not equivalent to a penetration test.
The final composition is defined in the diagnostic and technical proposal.
Discuss this projectMaaS® Architecture
Four layers, one integrated view
The primary layer guides the project. Technical dependencies may connect the delivery to other layers without expanding scope without approval.
Structural Foundation
Network, connectivity, computing, and technical foundations.
Shielding & Identity
Access, devices, collaboration, and security controls.
Business Continuity
Recovery, resilience, and interruption readiness.
Orchestration & Governance
Visibility, policies, indicators, and coordinated evolution.
Delivery process
Governance from discovery to handoff
- 01
Diagnostic and assessment
Understanding the environment, need, and relevant constraints.
- 02
Priorities and scope
Definition of deliverables, responsibilities, assumptions, and acceptance.
- 03
Solution design
Architecture, implementation plan, and technical decisions.
- 04
Governed implementation
Execution with change control and impact communication.
- 05
Validation and documentation
Testing, evidence, documentation, and open-item records.
- 06
Transition and evolution
Knowledge transfer and continuity definition, when contracted.
Common deliverables
Evidence to operate and decide
Artifacts are selected according to each project's type, size, and scope.
- Scope and responsibilities
- Implementation plan
- Relevant documentation and inventory
- Validation evidence
- Open items and recommendations
- Knowledge transfer
Not every project includes the same documents, tools, or a monthly operation. The technical proposal records exactly what will be delivered.
After delivery
MaaS® Operations & Support as optional continuity
The project may end after validation and handoff. When appropriate, Apix can provide support, monitoring, and evolution under a separate contract with its own responsibilities and SLA.
Explore MaaS® Operations & SupportFrequently asked questions
Before starting a project
Can I engage only one project?
Yes. A one-off project has its own scope, start, completion, and delivery criteria. Ongoing support is optional and contracted separately.
Does the diagnostic already define price and timeline?
The diagnostic gathers the information needed to size scope, dependencies, assumptions, investment, and schedule in a technical proposal.
Will the project interrupt operations?
Impacts and change windows are evaluated during planning. When relevant, the solution includes a pilot, communication, and rollback plan.
Can you work with our internal team or other vendors?
Yes, provided responsibilities, access, and interfaces are defined in the project scope and governance.
Does every project use all four MaaS® layers?
Each project has a primary layer. Other layers may be involved when dependencies exist, always within the approved scope.
Which IT improvement needs to move forward?
Start with a diagnostic to turn the need into clear priorities, scope, and next steps.