What does the A$300 per month support entry point mean?

The A$300 per month figure is the public entry point for retained support on lower-complexity environments. Actual inclusions, review cadence, coverage hours, and response targets need to be matched to the system and confirmed in the support schedule.

Does IATRT only support systems it originally built?

No. Support can include inherited environments, legacy controllers, existing infrastructure, and systems built by other vendors, provided the onboarding stage gives enough visibility to support them responsibly.

Is after-hours or emergency support available?

Higher-urgency and after-hours support may be available where the environment justifies it, but emergency responsiveness should be defined explicitly in the support agreement rather than assumed from a generic monthly plan.

Support

Retained support that starts small and scales with risk.

IATRT supports business systems, custom electronics, infrastructure, and mixed IT/OT environments with a documented model that starts from A$300/month and becomes more structured as criticality increases. The goal is transparent, optional, low-disruption support with security patching and justified change rather than churn for its own sake. This is not hypothetical packaging: Alabanos Taxi is a live fleet management and dispatch system under active support, including website, SEO, booking, dispatch workflows, customer/admin portals, SMS OTP, and taxi-management workflows.

Tiers

A public outline of the support model.

Essential

From A$300/month for lower-complexity or early-stage environments
Business-hours triage, planning, and documented next actions
Suitable for small business systems, prototypes, and steady-state assets that benefit from low-change oversight

Enhanced

Priority support, scheduled maintenance, and stronger monitoring coverage
Better fit for production systems with multiple dependencies
Used where security patching, backup review, reporting, and change planning need regular cadence

Mission-Critical

Explicit escalation paths, higher urgency planning, and tighter operational controls
Reserved for environments where downtime cost and safety implications are materially higher
Coverage, response targets, and standby expectations must be agreed in writing

Managed operations

Support is not just ticket response.

Onboarding & Health Check

Inherited environments are reviewed before they are accepted into support so hidden dependencies, documentation gaps, and obvious risks can be surfaced.

Monitoring & Visibility

Support can include monitoring, backup review, remote access checks, and system visibility appropriate to the environment rather than a generic MSP bundle.

Maintenance & Change

The default goal is minimal-invasive maintenance: security patches when needed, planned upgrades when justified, and no unnecessary churn against the system's operational constraints and service windows.

Escalation & Reporting

Criticality, escalation path, and reporting cadence are made explicit so support stays useful for operators, owners, and non-technical stakeholders.

Coverage

What the support model is designed to cover.

Business & Infrastructure

Servers, DNS, VPS, networking, backups, VPNs, and hosting workflows
Web platforms and internal tools that require operational continuity
Mixed Windows, Linux, and appliance environments

Custom Systems

Custom controllers, electronics, dashboards, and supporting software built for maintainability, upgradeability, and scale
Legacy and inherited systems where context recovery is part of the job
Rescue, stabilisation, and staged modernisation over time

Marine & Field Contexts

Assets that operate outside a normal office environment
Support structures that need realistic expectations around access and urgency
Monitoring, spares, rollback, and maintenance planning matched to operating conditions

Frequently Asked

What does the A$300/month entry point actually cover?

It is the published starting point for retained support on lower-complexity environments. The exact scope still needs to be defined: system count, criticality, support hours, monitoring depth, maintenance cadence, and whether the work is primarily reactive, proactive, or both. Support is optional and the goal is stable low-disruption maintenance, not forced change.

Do you have real customers on support tiers?

Yes. A public example is Alabanos Taxi - a live fleet management and dispatch system including booking, dispatch workflows, customer/admin portals, SMS OTP, and taxi-management provisioning. This reflects the same operations-aware systems IATRT designs, delivers, and supports for clients. Real customers, real usage, and active support tiers - not static portfolio work.

Do you only support systems you built yourself?

No. Inherited systems, legacy equipment, and other vendors' deployments can be supported if the onboarding stage provides enough visibility to do so responsibly. In some cases, the first job is stabilisation and documentation rather than immediate long-term support.

Is after-hours or emergency support included?

Higher-urgency support may be available, but it should be explicitly agreed in the support schedule. Public marketing copy should not be treated as an implied 24/7 emergency response commitment.

Delivery Framework

See how scoping, integration, testing, and handover are structured from first contact to ongoing care.

View framework

IP & Exit

Review the customer-owned IP position, migration intent, and change-control summary.

View IP & exit

Trust Pack

See the public notes on security, testing, and commercial clarity that sit behind the support model.

View trust pack