Quantonic

Home / Services / Cloud and DevOps

Practices

Cloud and DevOps, run as a managed service

Pipelines, environments, monitoring and restores looked after for a business whose releases depend on one person.

Twenty minutes, bring one problem. Onsite across Melbourne, remote for the rest.

The service

What the service covers

  • Build and release pipelines designed, maintained and fixed when they break, with quality gates before a release.
  • Infrastructure defined as code and changed through review, with drift from the code detected and reported.
  • AWS, Azure and Google Cloud environments kept patched, tagged and costed, with spend reported against the tags.
  • Logs, metrics, traces and alerts set so that a failure reaches someone.
  • Backups and restores tested on a schedule, with a recovery runbook and a failover drill.
How it runs

How the managed service works

  • Scope

    A Managed Service Schedule names the system, the category of work and a monthly capacity stated in tickets or hours, never in people.

  • Queue

    Requests go into one queue that Quantonic runs. Priorities and feedback come through that queue, not to individuals.

  • Monthly report

    Each month a written report sets out what was done against the service levels in the Schedule.

  • Stop condition

    If a service level is missed two months running, you can end the Schedule at that month's end.

Work is done inside your systems through accounts you issue and can revoke the same day. Anything that has to leave them is listed in the Schedule first.

An example request: a release pipeline that fails at a quality gate, fixed through a reviewed change to the pipeline code.

Accountability

Who is accountable

  • The person

    Amit Bhardwaj, founder and principal consultant, in Melbourne. I scope the work, review and accept it before it reaches you, and I am the person you call.

  • The contract

    Your contract is with Quantonic Legacy Innovations Pty Ltd, an Australian company, under the law of Victoria, whoever does the work.

  • Sign-off

    Changes are released with your sign-off and a rollback step, as the Schedule sets out.

Delivery

Who delivers the work

  • The firm

    Under a signed Schedule, the service on this page is delivered with TechSnitch, a technology services firm with delivery teams in India.

  • The agreement

    Work for a client starts only under a signed agreement between Quantonic and the firm, and runs through Quantonic's queue. The firm employs, pays and directs its own people.

  • What you do not get

    You do not direct individuals and nobody is offered or chosen by name to do the work. Names appear only where your access security needs them. The fee is for the service, never per person or per hour.

  • Where

    The Schedule names the firm's legal name and every country it delivers from before you sign. Where your rules do not allow access from outside Australia, the service is declined.

Honest limits

What is not claimed

  • Quantonic claims no AWS, Microsoft or Google partner status, for itself or for the delivery firm.
  • I have run no cloud or DevOps service for a client myself.
  • No uptime figure is promised beyond the service levels written in the Schedule.
  • No 24-hour on-call unless the Schedule says so.

Product and company names on this page are trade marks of their owners, used only to describe what the service relates to.

When to call

The situations that start a call

  • Releases are manual and depend on one person.
  • The cloud bill grew and nobody can say why.
  • An outage showed there was no alert, no runbook and no tested restore.

Bring one problem.

Twenty minutes on a call, then a written answer on whether and how the service can be set up.