Aim 4 The Cloud Inc. is a Canadian Managed Services Provider specializing in managed hosting, cloud infrastructure, backups, application migrations, consulting, development, security, and related technical services.

Rather than simply providing infrastructure and leaving clients to manage it alone, we combine technology with ongoing operational support, monitoring, troubleshooting, and technical guidance.

Aim 4 The Cloud was founded in 2016 by a team of longtime technology professionals who had previously worked together at GT.net.

Our headquarters are in Vancouver, British Columbia, Canada.

Telephone: +1 778 819 7048

No. Although we are headquartered in Canada, we can support organizations with distributed teams, international users, and infrastructure requirements spanning multiple regions.

We support organizations of different sizes and levels of technical maturity, including small and medium-sized businesses, professional-services firms, technology companies, developers, agencies, non-profit organizations, e-commerce businesses, and companies operating customer or employee applications.

The most appropriate service depends on the application, performance, security, budget, availability, and management requirements.

Yes. Our managed services are particularly useful for organizations that need reliable technology but do not want to build a complete in-house infrastructure and systems-administration team.

Yes. We can work as an extension of an internal IT team and coordinate with software developers, application vendors, security professionals, and other service providers.

Responsibilities are documented so each party understands who manages the infrastructure, application, data, testing, security, and business decisions.

Commodity hosting is commonly designed around automated provisioning and narrow support boundaries. Aim 4 The Cloud takes a more involved approach.

Our clients gain access to professionals who can help plan, configure, monitor, troubleshoot, migrate, secure, and expand their environments. Consulting, migration, development, and project assistance can also be incorporated when standard hosting support is not enough.

Aim 4 The Cloud may provide, arrange, resell, configure, manage, or support infrastructure and technology supplied through carefully selected data-centre, network, hardware, software, licensing, or service partners.

Aim 4 The Cloud remains the client’s managed-services contact for the responsibilities defined in the service order. Applicable third-party products may also be subject to supplier terms.

Yes. Many business applications do not fit neatly into a predefined package. We can design an environment using an appropriate combination of shared hosting, managed virtual machines, dedicated hardware, private networking, managed firewalls, private cloud infrastructure, email hosting, backups, monitoring, migration assistance, development, and consulting.

Managed hosting means Aim 4 The Cloud takes responsibility for defined operational components of the hosting environment rather than only supplying raw computing resources.

Depending on the selected service, managed responsibilities may include:

• Initial provisioning and operating-system deployment
• Platform and infrastructure administration
• Monitoring and troubleshooting
• Security and network configuration
• Backup operations and recovery assistance
• Maintenance, capacity planning, and technical guidance
• Coordination with relevant vendors

The exact division of responsibility is documented in the applicable service order.

Not automatically. Managed hosting generally covers the infrastructure and agreed platform components.

Application support, source-code changes, plugin troubleshooting, database development, custom integrations, content management, and vendor-specific application work may require a separate support arrangement or project scope.

Unless specifically included in writing, clients generally remain responsible for their business processes, application content and data, user administration, application-specific testing, software licensing, legal and regulatory requirements, client-controlled credentials, and components designated as client-managed.

Yes. Proactive monitoring is available across managed hosting environments and is included with services such as Managed Virtual Machines.

The monitored components and alert thresholds depend on the selected service and agreed management scope.

No. Monitoring improves visibility and response, but no provider can guarantee that hardware, software, applications, networks, suppliers, or internet services will never experience a failure.

Any formal availability commitment, response target, or service credit applies only where it is included in the applicable service-level agreement or service order.

Managed Virtual Machine services include access to 24/7 technical support for infrastructure incidents, troubleshooting, recovery requests, and hosting guidance. Other services may have support coverage defined by their individual plan or service order.

Standard support addresses the operation of service components included in your plan.

Professional services cover additional hands-on work such as complex migrations, application troubleshooting, custom configurations, development, architecture design, security remediation, major restorations, vendor coordination, and work outside the normal support scope.

Yes. Aim 4 The Cloud provides a customer portal for account and service management.

Depending on the service, the portal may provide access to service information, invoices, support functions, DNS management, server-management features, and network-edge firewall configuration.

Yes. A service can be structured around a clearly defined management boundary. For example, Aim 4 The Cloud may manage infrastructure and networking while your internal team or application vendor manages the application itself.

The best service depends on the application and business requirements:

• Shared Web Hosting suits many standard websites and supported PHP applications that do not require a dedicated operating system.
• Managed Virtual Machines suit applications requiring dedicated resources, operating-system access, custom software, greater isolation, or private networking.
• Managed Dedicated Hardware suits workloads requiring physical resources dedicated to one client, predictable performance, large resource allocations, or hardware-level isolation.
• Managed Private Cloud suits organizations operating multiple workloads that need a more scalable, highly available, and centrally managed infrastructure.

Yes. An organization may begin with shared hosting or a single Managed Virtual Machine and later expand into multiple servers, private networking, dedicated hardware, managed firewall protection, or private cloud infrastructure.

Yes. A solution can combine public-facing web servers, private database servers, managed email hosting, dedicated hardware, managed virtual machines, private networks, managed firewall pairs, load balancing, DNS hosting, backup services, monitoring, development, and migration support.

Yes. A discovery or consulting engagement can document existing servers, applications, databases, storage, traffic, security controls, dependencies, recovery needs, performance concerns, and future plans.

Some services may be offered through predefined packages, while others require a custom quotation.

Private cloud, dedicated hardware, complex migrations, managed firewalls, and multi-system environments are normally priced according to capacity, licences, management scope, backup requirements, networking, support, and contract term.

Yes. Temporary development, testing, staging, migration, campaign, demonstration, and event environments can be discussed. Availability, minimum terms, security, backup retention, and decommissioning responsibilities are confirmed before deployment.

We review current utilization, application architecture, expected growth, peak demand, resilience requirements, storage, network traffic, and operational constraints before recommending a design. Capacity can then be adjusted as real usage becomes clearer.

Managed Shared Web Hosting provides an account-level website environment without making the client responsible for operating the underlying server.

Clients receive tools for managing website files, databases, domains, FTP access, and supported application settings while Aim 4 The Cloud manages the server-level platform.

It is suitable for many business websites, WordPress websites, portfolios, corporate sites, landing pages, campaigns, non-profit sites, agency projects, developer projects, staging sites, and supported PHP applications.

Applications needing dedicated resources, specialized software, strict isolation, consistently high traffic, or administrative operating-system access may be better suited to a Managed Virtual Machine.

Yes. Clients receive access to a CWP user panel for common website-management tasks, including eligible file management, FTP management, database administration, domain organization, resource information, supported PHP settings, and application configuration tools.

Depending on the selected package, an account may support multiple domains or website projects. Package-specific domain, storage, database, and FTP limits are confirmed before ordering.

Yes. Shared Web Hosting accounts are backed up nightly with a rolling 14-day retention period. Project-specific backups can also be arranged for major changes, migrations, or deployments.

No. Aim 4 The Cloud intentionally separates website hosting from email hosting. This reduces the number of critical services dependent on one platform. Managed Email Hosting is available as a separate service.

DNS is managed separately from the website-hosting control panel. This supports a cleaner architecture and prevents website-platform changes from unnecessarily affecting DNS services.

Yes. Website migration is available as an optional professional service and may include reviewing the source environment, transferring files and databases, updating configuration, checking PHP compatibility, preparing the destination, coordinating cutover, testing, and troubleshooting.

Yes. Eligible WordPress installation, deployment, configuration, compatibility, migration, and recovery work can be provided as project support. Theme, plugin, code, content, and third-party vendor issues are reviewed individually.

Supported websites can use encrypted HTTPS connections. Assistance with eligible certificate deployment or troubleshooting can be provided within the applicable service scope.

A Managed Virtual Machine is an isolated virtual server environment with resources assigned specifically to the client’s workload.

It is a strong fit when an application needs dedicated CPU, memory, and storage; administrative operating-system access; custom dependencies; greater isolation; custom networking; or more flexibility than shared hosting.

An unmanaged VPS generally provides server access while leaving monitoring, security, backups, configuration, troubleshooting, and maintenance to the customer.

An Aim 4 The Cloud Managed VM combines virtual infrastructure with proactive monitoring, snapshot protection, network security features, DNS hosting, private-network capability, and technical support.

Managed Virtual Machines can support eligible Linux, BSD, and Microsoft Windows Server operating systems. The specific version depends on application compatibility, vendor support, licensing availability, and security requirements.

Microsoft Windows deployments are subject to applicable licensing fees.

Managed VM environments include snapshot recovery points maintained on a seven-day rotation. Additional backup strategies can be designed for databases, longer retention, compliance, or specialized recovery objectives.

Yes. Managed VMs benefit from anti-DDoS protection supplied through the underlying data-centre network. No DDoS service can guarantee that every attack will have no effect, but network-level mitigation provides an important additional layer of protection.

Yes. Managed VM customers can configure supported network-edge firewall rules through the server manager in the Aim 4 The Cloud client portal. These rules complement, rather than replace, operating-system and application security controls.

Yes. Supported servers and services can be connected through an isolated private network, allowing databases, management services, storage systems, and backend components to remain off the public internet.

Managed VM clients receive access to basic DNS hosting through the Aim 4 The Cloud client portal. Specialized DNS services or third-party premium features may be quoted separately.

In many cases, resources can be increased or the environment can be expanded with additional servers. Some changes may require a maintenance window, data migration, operating-system work, or movement to a different configuration.

Yes, where the selected resources, storage, backup design, security, and application architecture are appropriate. Database-specific administration or tuning may require an additional management or professional-services scope.

Managed Dedicated Hardware provides a physical server whose computing resources are dedicated to one client rather than shared with unrelated workloads.

Aim 4 The Cloud manages the agreed operating, monitoring, networking, security, and support responsibilities.

Dedicated hardware may be appropriate for resource-intensive applications, large databases, high sustained processor or memory usage, storage-heavy workloads, physical-server isolation, hardware-specific licensing, or environments that have outgrown smaller virtual infrastructure.

Yes. Supported dedicated systems can be connected through dedicated private networking for application, database, storage, replication, backup, and management traffic.

Available dedicated environments can include network-level DDoS mitigation and controlled public connectivity. Additional security can be introduced through operating-system firewalls, edge controls, private networking, or a Managed Virtual Firewall.

Backups are available as an optional add-on for Managed Dedicated Hardware. The backup design is selected according to data volume, application type, change rate, recovery objectives, retention requirements, and available maintenance windows.

Yes. Dedicated servers can be combined with Managed Virtual Machines, private network segments, managed firewalls, storage, backup systems, and other infrastructure.

Available processor, memory, storage, disk layout, network, and regional options depend on current inventory and the underlying infrastructure platform. Requirements are confirmed during quotation.

A Managed Private Cloud is a dedicated cloud environment designed for organizations operating multiple virtual machines, applications, or business services.

It provides a foundation for workload isolation, centralized management, scalability, availability planning, private networking, and infrastructure growth.

A Managed VM provides one managed virtual server. A private cloud provides a broader infrastructure platform capable of supporting multiple virtual machines, networks, application tiers, and operational requirements.

Private cloud may suit organizations operating several business-critical applications, multiple production and development environments, stronger workload separation, ongoing infrastructure growth, server consolidation, or long-term application modernization.

In many cases, yes. The migration process depends on the source platform, virtual-machine format, operating systems, licences, network design, dependencies, data volume, and allowable downtime.

Yes. Private networking can separate application, database, management, backup, development, and other workload tiers. Managed firewall services can control how users, offices, partners, and public traffic reach those environments.

No. High availability, replication, snapshots, and backups solve different problems. Backups remain necessary for recovery from accidental deletion, corruption, application errors, security incidents, or unwanted changes replicated across the live environment.

Private cloud can be designed to reduce selected single points of failure and support highly available application architectures. The actual availability level depends on the infrastructure design, application design, licensing, networking, storage, and service order.

Managed Email Hosting provides business email under the client’s own domain without requiring the client to operate the underlying email servers.

Depending on the selected package, features may include business-domain mailboxes, browser-based webmail, desktop and mobile compatibility, shared calendars, shared address books, calendar and contact synchronization, mobile synchronization, spam filtering, malware scanning, secure connections, and mailbox administration through the Aim 4 The Cloud portal.

Managed Email Hosting includes mailbox-data backups on a rolling 14-day rotation. Backup restoration is intended for eligible data-loss events and is not a permanent legal-retention or compliance-archive service unless separately arranged.

Yes. Standard compatible desktop and mobile email applications can be configured using supported secure mail protocols. Calendar, contact, and mobile synchronization capabilities depend on the client software, device, operating system, and service configuration.

Yes. The platform includes layers intended to identify spam, malicious attachments, malware, and other unwanted email. No filtering system can identify every unwanted message without occasionally permitting a harmful message or blocking a legitimate one.

Yes. Email migration can be provided as a scoped project and may include mailbox discovery, account creation, data transfer, DNS preparation, synchronization, client-device coordination, cutover, and validation.

A carefully planned migration can substantially reduce risk, but a universal no-loss guarantee is not appropriate without assessing the source platform and migration method. Where supported, data may be synchronized in stages with a final synchronization near cutover.

Standard mailbox backups are not the same as long-term compliance archiving. Organizations requiring immutable retention, legal hold, e-discovery, or extended retention should discuss a dedicated archival solution.

Yes. Eligible mailbox and domain-management functions are available through the Aim 4 The Cloud client portal according to the selected service and assigned permissions.

A Managed Virtual Firewall is a professionally managed security gateway placed between private networks and public or external connections.

It can control how traffic enters, leaves, and moves between application environments. Aim 4 The Cloud handles deployment, policy configuration, monitoring, maintenance, troubleshooting, VPN setup, and eligible ongoing changes.

Operating-system firewalls protect individual servers, while a dedicated network firewall adds centralized control before traffic reaches those servers.

It can publish only approved services, keep backend systems private, control outbound traffic, segment application tiers, centralize policies, provide VPN connectivity, and support network-level logging.

Yes. Aim 4 The Cloud Managed Virtual Firewalls are deployed as synchronized high-availability pairs, reducing the risk that a single firewall instance becomes a single point of failure.

Yes. The firewall can act as the controlled gateway between private VLANs and the public WAN. Approved applications can be published while databases, management systems, storage, and backend components remain private.

Yes. Network segmentation can separate public web systems, application servers, database servers, management systems, development environments, backup networks, monitoring systems, and internal business services.

Yes. Managed IPsec tunnels can securely connect supported office networks, data centres, cloud environments, partners, and other authorized locations.

Supported remote-access VPN services can be configured where appropriate. User authentication, device requirements, permissions, encryption, and support responsibilities are established during design.

Yes. Managed firewall environments can provide application load-balancing capabilities for eligible TCP, HTTP, and HTTPS services using health checks and suitable traffic-distribution policies.

Yes. Firewall and edge-security policies can limit administrative ports or services to approved source networks and addresses. VPN access, multi-factor authentication, private management networks, and operating-system firewalls may also be recommended.

Yes. Firewall-policy review, cleanup, documentation, migration, and redesign can be provided as a consulting or project engagement.

We can assist with websites, business applications, customer portals, content-management systems, e-commerce platforms, Linux, BSD and Windows servers, virtual machines, databases, storage, development environments, production systems, on-premises infrastructure, provider-to-provider transitions, legacy platforms, and multi-server applications.

Usually not. Applications may depend on databases, storage, scheduled jobs, background services, identity systems, APIs, certificates, DNS, firewall rules, private networks, monitoring, backups, and third-party integrations.

A managed migration may include discovery and assessment, destination design, project planning, environment preparation, data transfer and synchronization, application testing, production cutover, and post-migration stabilization.

Yes, subject to having the required access, cooperation, credentials, data-export methods, and technical information. Source-provider restrictions can affect the available migration method.

Yes. We can assess on-premises applications and plan their transition into Managed Virtual Machines, dedicated hardware, private cloud, or another appropriate destination.

No responsible migration provider should make a generic zero-downtime promise without understanding the application. Some systems support replication, staged synchronization, parallel operation, or traffic switching; others require a maintenance window.

Depending on the application, we may prepare the destination in advance, complete an initial transfer, perform incremental synchronization, reduce DNS time-to-live values, test through isolated access, schedule a maintenance window, pause changes, complete a final synchronization, redirect traffic, and validate immediately after cutover.

Where technically possible, yes. A rollback plan may define trigger conditions, decision authority, how long the old environment remains available, how traffic and configuration changes are reversed, and how stakeholders are informed.

Testing is normally shared. Aim 4 The Cloud can validate infrastructure, connectivity, operating services, certificates, monitoring, backups, and agreed technical functions. The client, application owner, or software vendor usually confirms business workflows and application-specific behaviour.

Yes. We can coordinate requirements, access, testing, cutover steps, troubleshooting, and responsibilities with developers, software vendors, internal IT teams, and other third parties.

Yes. Depending on the application, the strategy may involve rehosting, replatforming, refactoring, consolidation, or retirement and replacement of obsolete components.

Useful information includes server inventory, operating systems, application architecture, database types and sizes, storage volume, change rate, user count, traffic, DNS, certificates, integrations, scheduled jobs, authentication systems, firewall requirements, compliance needs, existing backups, acceptable downtime, target date, and source-provider access.

Yes. A phased migration can move selected applications, servers, databases, or user groups first. Dependencies and temporary connectivity between the old and new environments must be planned carefully.

Consulting may include cloud strategy, infrastructure architecture, security reviews, network design, backup and recovery planning, migration planning, capacity planning, technology assessments, vendor coordination, project management, application hosting design, legacy-system modernization, and operational process improvement.

Yes. Aim 4 The Cloud can develop eligible custom applications, integrations, automation, web solutions, and supporting tools. Development engagements begin with requirements gathering and a defined scope.

Potentially. We first review source code, documentation, dependencies, licences, security, deployment processes, and the overall condition of the application. Some systems may require remediation, vendor involvement, redevelopment, or a limited best-effort arrangement.

Yes. Where technically suitable, custom automation can connect systems, transfer data, generate notifications, schedule tasks, reduce repetitive administration, or improve operational visibility.

Yes. Clients may engage Aim 4 The Cloud for a specific migration, deployment, troubleshooting, security, infrastructure, or development project without purchasing every available managed service.

Yes. Platform-neutral discovery and architecture work can help define requirements, compare approaches, identify risks, and establish a practical roadmap before infrastructure is ordered.

Backup inclusion and retention depend on the service:

• Shared Web Hosting: nightly backups with a 14-day rotation
• Managed Virtual Machines: snapshots with a seven-day rotation
• Managed Email Hosting: mailbox-data backups with a 14-day rotation
• Managed Dedicated Hardware: backups available as an optional add-on
• Custom and private-cloud environments: backup design confirmed in the service order

A rotation keeps a defined series of recent recovery points. For example, a seven-day rotation generally maintains recovery points from the recent seven-day period as newer backups replace older ones. It does not retain every version indefinitely.

Not always. Snapshots are useful for rapidly restoring a virtual machine to a recent system state, but they may not satisfy long-term retention, application consistency, or disaster-recovery requirements.

The available restoration level depends on the service and backup format. Some systems support granular restoration, while others may require restoring an account, mailbox, database, server, or complete snapshot.

Routine restoration assistance may be included with some services. Complex, repeated, urgent, application-specific, historical, or customer-caused recovery work may incur professional-service or restoration charges.

No backup system can guarantee that every file, message, database, configuration, or point in time will always be captured and recoverable. Clients should maintain independent copies where data loss would create serious harm.

Yes. Longer retention, additional backup frequency, off-platform storage, database-aware protection, or specialized recovery arrangements can be discussed.

Yes. Disaster-recovery planning may identify critical applications, define recovery priorities and objectives, review dependencies, design backup and replication, document procedures, assign responsibilities, plan communication, and conduct recovery tests.

Yes. Scheduled restoration tests or disaster-recovery exercises can be included in a custom service or professional-services engagement. Testing scope and frequency should reflect the importance of the workload.

Controls vary by service and may include network-level DDoS mitigation, edge firewall controls, managed firewalls, private networking, segmentation, monitoring, secure administrative access, operating-system hardening, security updates, spam and malware filtering, backup protection, VPN connectivity, access controls, logging, and alerting.

No provider can make that guarantee. Internet-connected technology involves changing threats, software vulnerabilities, credential risks, third-party dependencies, and human error.

Multi-factor authentication is used or recommended where supported and appropriate. Availability depends on the customer portal, operating system, application, VPN, email client, and other technology involved.

Clients are responsible for protecting client-controlled passwords, private keys, API keys, authentication devices, and other credentials. Access should be removed promptly when a person no longer requires it, and suspected compromise should be reported immediately.

Customer data may be processed in Canada and in other locations where Aim 4 The Cloud or its authorized subprocessors operate. Any required country, region, or data-residency commitment must be written into the service order.

A Canadian data-residency requirement can be assessed, but it must be expressly confirmed in the service order. The design must consider primary infrastructure, backups, monitoring, support access, software providers, and subprocessors.

Yes. Aim 4 The Cloud may use authorized infrastructure, software, network, data-centre, payment, licensing, or support providers as part of service delivery.

Potentially, depending on the service, information type, safeguards, location, and applicable laws. The client remains responsible for identifying its legal and regulatory requirements and ensuring the selected service is appropriate.

Highly regulated information should not be placed into a service unless the applicable service order expressly confirms that the service is suitable. A separate security, privacy, compliance, or architecture review may be required.

Aim 4 The Cloud operates under applicable Canadian privacy obligations. The laws relevant to a specific engagement depend on the client, information, processing activity, industry, and location.

Aim 4 The Cloud will handle notification according to applicable law and the governing agreement. Available information may be updated as investigation and remediation progress.

No. Automated tools or limited manual review may be used when reasonably required to provide requested support, detect spam or malware, investigate suspected abuse, protect services, or comply with law.

Security testing must be lawful, appropriately contained, within an authorized scope, and expressly permitted by the service order or approved by Aim 4 The Cloud in writing. Testing must not affect other customers or systems outside the authorized scope.

Yes. Eligible remediation can be provided as managed work or professional services, depending on whether the affected infrastructure, operating system, application, code, or third-party product falls within the agreed support scope.

Support can be requested through available customer-support channels, including the Aim 4 The Cloud client portal. Emergency and routine requests should identify the affected service, impact, symptoms, recent changes, timestamps, and authorized contacts.

Useful information includes the affected domain or service, when the issue began, who is affected, exact errors, recent changes, screenshots where appropriate, reproduction steps, business impact, available workarounds, and relevant vendor contacts.

An emergency generally involves a serious active impact such as a production service being unavailable, a significant security incident, widespread inability to access a critical service, a major network failure, severe data-access problems, or a time-sensitive recovery request.

Yes, where vendor coordination is included or approved as professional-service work. The client may need to authorize Aim 4 The Cloud with the vendor and remain involved in licensing, commercial, or business decisions.

Planned after-hours work can be arranged for migrations, maintenance, upgrades, and changes that could affect production users. Scheduling, minimum charges, staffing, vendor availability, and rollback requirements are confirmed during planning.

Routine managed-service work may be performed according to the agreed operating scope. Material customer-requested changes are normally approved through an authorized contact. Immediate protective action may be taken when reasonably necessary to address a security threat or material service risk.

Yes. Clients should maintain current administrative, billing, security, and technical contacts. Permissions can be limited so only appropriately authorized individuals can request sensitive changes or approve service modifications.

Change documentation depends on the service and project scope. Material planned work can include implementation steps, maintenance windows, validation, rollback planning, and completion notes.

1. Contact Aim 4 The Cloud.
2. Describe the business and technical requirement.
3. Complete discovery where necessary.
4. Review the proposed solution.
5. Accept the quotation or service order.
6. Provide required access and information.
7. Complete provisioning or migration.
8. Test the service.
9. Enter normal managed operations.

Requirements may include business and billing information, authorized contacts, domain information, application documentation, current-provider access, server credentials, DNS access, licences, vendor contacts, network information, security requirements, user lists, testing contacts, and maintenance-window approval.

Activation time depends on the service, resource availability, licences, migration requirements, client readiness, and third-party dependencies. Published or discussed dates are estimates unless expressly guaranteed in the service order.

Billing normally begins according to the service commencement date, quotation, or service order. Setup and initial fees may be required before activation.

Yes. Provisioning or migration may be delayed when required credentials, licences, approvals, data, testing, vendor cooperation, or technical information are unavailable.

For projects and custom services, onboarding requirements can be documented as a checklist or project plan so responsibilities, access, testing, and target dates are clear.

Unless the service order states otherwise, fees are quoted and payable in Canadian dollars. Currency-conversion charges imposed by a payment provider remain the client’s responsibility.

Applicable taxes are additional unless expressly stated otherwise.

Some services require setup, provisioning, migration, hardware, licence, or project fees before activation. Applicable initial and recurring charges are listed in the quotation or service order.

Recurring fees are normally billed in advance. Usage charges, overages, professional services, third-party charges, and other variable amounts may be billed in arrears.

Available payment methods are shown through the quotation, invoice, or customer portal and may include an approved credit card, bank account, pre-authorized debit, or another supported method.

Unless the applicable service order states otherwise, a service may automatically renew after its initial term. Applicable notice requirements are defined by the service order and Terms of Service.

Some services may be offered monthly, while others require a fixed commitment because they involve reserved infrastructure, hardware, software licences, supplier commitments, or term-based pricing.

A fixed-term service may be subject to early termination charges, non-cancellable supplier costs, remaining licensing commitments, or repayment of discounts conditioned on completion of the term.

Refundability is governed by the applicable agreement and law. Project deposits, purchased licences, provisioned hardware, third-party commitments, and completed professional services may be non-refundable.

Contact Aim 4 The Cloud promptly with the invoice number, disputed amount, reason for the dispute, and supporting information. Undisputed amounts remain payable when due.

Aim 4 The Cloud may provide notice and suspend some or all services until the account is brought current. Overdue charges, interest, reconnection costs, collection expenses, or other permitted charges may apply.

The service order, quotation, statement of work, or similar ordering document describes the purchased service. The governing documents and their order of precedence are defined in the applicable agreement.

The agreement may be accepted through an online checkout, customer portal, confirmation email, signed service order, electronic signature platform, or use of the service after applicable notice, as permitted by the agreement and law.

When a service expires or terminates, the right to use the affected service ends, outstanding fees become due, provider-issued access may end, assigned network resources must be relinquished, and customer data may be deleted according to the agreement and retention practices.

Data-export or migration assistance may be available when requested before deletion and where export is technically possible. Professional-service charges may apply.

Retention depends on the service, technical platform, backup rotation, service order, and applicable law. Clients should not assume that online or backup data will remain available after termination.

Not necessarily. Data may remain temporarily within protected backups until those backups expire or are overwritten through their ordinary rotation.

IP addresses and network resources assigned as part of a service remain under the control of Aim 4 The Cloud or the applicable supplier and must normally be relinquished when the service ends.

Export and transition planning should begin well before the termination date. This allows time to confirm formats, data volume, transfer methods, credentials, DNS changes, and any professional services required.

Services may be used for lawful business, organizational, professional, development, testing, communications, hosting, storage, security, and related purposes permitted by the agreement and service order.

Yes. Prohibited uses include unlawful activity, fraud, phishing, malicious software, unauthorized access, intellectual-property infringement, spam, abusive traffic, denial-of-service activity, unlawful surveillance, privacy violations, and activity that unreasonably interferes with services or other customers.

Commercial electronic messages must comply with Canada’s anti-spam legislation and all other applicable requirements. Clients must have required consent, provide accurate sender information, and include a working unsubscribe method.

Notify Aim 4 The Cloud immediately. We may restrict access, isolate systems, block traffic, suspend affected components, reset credentials, or take other reasonable protective action while the incident is investigated.

Yes. A service may be suspended when Aim 4 The Cloud reasonably believes an account, system, credential, application, or data set has been compromised, or when traffic or content poses a material threat.

Review the current Terms of Service and Acceptable Use Policy. The applicable service order may contain additional requirements.

No. Begin with the business problem, application, users, current challenges, expected growth, security needs, and budget. Our team can translate those requirements into an appropriate technical design.

Helpful information includes what the application does, who uses it, where it runs today, current concerns, required operating system, approximate storage and traffic, security or compliance requirements, target date, acceptable downtime, available development or vendor support, and expected growth.

Yes. Once the requirements are sufficiently understood, Aim 4 The Cloud can prepare a quotation, service order, statement of work, or proposed architecture. Complex environments may require a paid discovery phase first.

The team confirms contacts, access, prerequisites, schedule, responsibilities, billing, and technical requirements. Infrastructure is then provisioned or the project begins according to the agreed scope.

Yes. Many clients begin with one hosting service, migration, or consulting project and later add infrastructure, backups, email, private networking, managed security, development, or ongoing support.

Use the contact form on the Aim 4 The Cloud website, call +1 778 819 7048, or use the customer portal if you are already a client.