About Celestique Cloud
What we are,
and how we work.
Our Story explains why this company exists. This page covers the operational detail: where we are based, how an engagement actually runs, what you receive, who is accountable for what, and the limits we place on our own claims.
Company identity
An Australian-led AI, data, cloud and security consultancy.
Celestique Cloud is a technology consultancy based in Mitcham, Melbourne. We help organisations modernise ageing systems, establish secure Azure or AWS foundations, activate trusted data, implement practical AI with a measurable business case, and operate the resulting environment after launch.
The six service domains are connected on purpose. Most of the problems clients bring us sit across more than one of them: an AI request that is really a data problem, a cost problem that is really a governance problem, a migration that is really a question about who will run the result. Scoping them separately is what produces the expensive version.
The founding belief behind that approach is covered on Our Story. This page stays with the facts.
- Where we are
- 16 Creek Road, Mitcham VIC 3132, Australia. Melbourne is our only location, and every engagement is scoped and coordinated from it.
- What we do
- Artificial intelligence, data and analytics, cloud modernisation, security and governance, platform engineering, and managed services.
- Platforms
- Microsoft Azure and Amazon Web Services, plus hybrid architectures where the assessment supports one.
- How we start
- With an assessment. The platform, the architecture and the size of the engagement are outputs of it rather than inputs to it.
- Sectors
- Construction and property, manufacturing and distribution, logistics and warehousing, professional services, and healthcare and community services.
- Commercial model
- Consulting and managed services only. We do not resell licences or cloud subscriptions, so no recommendation we make carries a margin for us.
Australian-led delivery
Scoped, decided and coordinated from Melbourne.
Melbourne-based, Australian-led and globally capable. In practice that means the thinking and the accountability sit in one place.
We operate from a single Australian location and do not run international offices. Where specialist capability is brought in for a piece of work, it is coordinated through the Melbourne lead who scoped it, and that person remains your point of accountability.
- Scoping, architecture decisions and client communication run from Melbourne.
- The consultant who scopes the work stays involved through delivery, so the recommendation and the result belong to the same people.
- Planning, reporting and escalation conversations are scheduled in Australian business hours.
- Australian privacy, procurement and record-keeping expectations are treated as design inputs rather than late corrections.
- Where the location of your data matters, it becomes a written design requirement and we tell you what the chosen services actually commit to.
- Coverage hours for any ongoing service are agreed per engagement and written into the service description.
Consulting approach
Outcome, return and risk before technology.
Clients usually arrive with a solution already in mind. We start one step earlier, with three questions that decide whether the solution is the right one.
- What changes?
- The outcome stated in business terms, with the measure that would tell you it worked. If that sentence cannot be written, the work is not ready to start.
- What does inaction cost?
- Hours, rework, delay, exposure or revenue left on the table. A proposal without a cost of doing nothing is a preference, not a business case.
- What risk does it carry?
- What breaks if the change goes wrong, who is affected, and who carries the consequence. Risk is priced into the plan rather than discovered during it.
Discover to Operate
Every engagement follows the same six-stage sequence, with a decision point at the end of each stage. You can continue, change direction, pause or take the work in-house at any of them, and the scope is written so that stopping is not a penalty.
- 01
Discover
Understand the business challenge, its cost and who it affects.
- 02
Assess
Review the current state, readiness, risk and commercial case.
- 03
Design
Shape the architecture, controls and success criteria.
- 04
Build
Implement in increments with evidence at every stage.
- 05
Adopt
Enable the people who use it and prove the outcome.
- 06
Operate
Run, monitor and improve the environment after go-live.
Azure and AWS
Dual-platform in practice, not just in the brochure.
Plenty of consultancies list both clouds and only staff one. We build and operate on both, which is the only position that makes an independent recommendation possible.
- Both platforms, in delivery
- We design, build and operate on Azure and on AWS. Neither is a fallback offered when a client insists.
- Chosen after assessment
- Existing investment, team skills, workload behaviour, data gravity, risk position and commercial objectives are reviewed before a platform is named.
- Written with its reasoning
- The recommendation records the options considered and why the others were rejected, so you can challenge it rather than accept it.
- Hybrid is a valid answer
- Keeping a workload where it is, or splitting across platforms, is a legitimate outcome when the assessment supports it.
- No margin either way
- We are not a reseller. There is no licensing revenue, quota or rebate attached to the platform we recommend.
- No partner claims
- We do not claim partner status, competency or tier with Microsoft or AWS anywhere on this site, and vendor icons identify technology rather than endorsement.
Every service domain has an Azure path and an AWS path, documented separately, so you can see what the work looks like on the platform you are considering before you commit to it.
Security and governance
Designed in at the start, because it cannot be added at the end.
Retrofitting identity, logging or data controls onto a running platform costs several times what it costs to design them in, and it usually happens under pressure.
We are a consultancy, not a certification body. We do not hold formal compliance certifications on your behalf and we do not guarantee a regulatory outcome. What we do is document the controls that exist, the gaps that remain, the risk each gap carries and the evidence an assessor would ask for.
- The identity and access model is decided before the first workload moves.
- Data classification and handling rules are agreed before data is copied anywhere.
- Logging, monitoring and alerting are specified as part of the build, not retrofitted after an incident.
- Secrets, keys and credentials sit in managed services from the first deployment.
- Policy and cost guardrails are applied at the subscription or account level, so drift is visible.
- Network exposure and administrative access are reviewed as design decisions with named owners.
- AI systems are reviewed for prompt-injection exposure, output handling and human oversight before release.
- A change and rollback path is agreed before go-live rather than improvised during one.
Operating model
How an engagement actually runs.
The part most consultancy pages leave out. This is the mechanism: what gets written down, who decides what, what you keep, and what happens when we disagree with you.
The shape of the work
Work starts with a written scope that states the outcome, the success criteria, the assumptions it depends on and the things it deliberately excludes. Exclusions matter as much as inclusions, because most disputes come from something both sides assumed the other was covering.
Delivery runs in increments with a review at the end of each. Nothing is reported as complete until you can see it working in your own environment, against the criteria agreed at the start. If an increment shows that the plan was wrong, we would rather say so at that review than at handover.
Engagements are sized so that stopping is always an option. A discovery can end at a recommendation. An assessment can end with you taking the work in-house. Neither is treated as a failure, and neither triggers a penalty.
What you receive
Artefacts vary with the engagement, but this is the standing list. All of it is written to be usable by your team without us in the room.
- A written scope with success criteria, assumptions and explicit exclusions.
- A current-state assessment with findings ranked by cost and risk rather than by ease.
- An architecture decision record for every significant choice, including the options rejected.
- A security and governance design covering identity, data handling, logging and guardrails.
- Infrastructure as code and pipeline definitions held in your repository, not ours.
- Runbooks and a handover pack written for your team to use without us.
- A test and acceptance record showing what was verified and how.
- A cost model with the assumptions that drive it made visible.
- A closing report covering what changed, what remains open and what we recommend next.
How decisions get made
Decisions are recorded so that a new person can read why the environment looks the way it does two years later, and so that nobody has to rely on memory of a meeting.
- One named decision-maker on your side and one on ours, agreed before work begins.
- Significant choices are recorded as decision records: what was decided, by whom, on what evidence, and what would justify revisiting it.
- Anything that moves scope, cost or risk is raised in writing as a change, and work on it waits for a decision.
- Disagreement is documented rather than smoothed over. If you choose an option we advised against, both positions are recorded.
- Progress is reported against the agreed success criteria, not against hours consumed.
- Code, infrastructure definitions, documentation and accounts remain yours throughout, so you can end an engagement without losing the work.
Who is responsible for what
Agreed at kick-off and written into the scope. An engagement that is vague about this is an engagement that will be late.
Celestique Cloud is responsible for
- The recommendation and the reasoning behind it.
- Architecture, build quality and delivery against the agreed design.
- Security controls implemented as designed, with evidence that they work.
- Documentation, handover material and knowledge transfer to your team.
- Raising risk, scope drift and cost change early and in writing.
- Meeting the acceptance criteria set at the start rather than the ones that would be easier to meet at the end.
Your organisation is responsible for
- A named decision-maker who can approve scope, cost and risk.
- Timely access to systems, data, accounts and the people who do the work.
- Ownership of licences, subscriptions and cloud accounts, which stay in your name.
- Internal approvals, change windows and communication to affected teams.
- Business context: what is genuinely being measured, and what is fixed for reasons outside the technology.
- The final decision on every recommendation, including the ones we advise against.
When the honest recommendation is to do less
Some engagements should be smaller than the enquiry that started them. Saying so reduces the value of the work in front of us, and it is still the recommendation.
When the assessment points to a smaller answer, we put both options in writing: the one you asked for, the one we recommend, what each costs, and what each leaves you with in two years. The choice stays yours. If the right next step is something your own team can do, we will say that too, and hand over the assessment that explains it.
The alternative is billing for work that will not hold up, which costs us a client and a reference at exactly the point we would want both.
- A dashboard request
- Reporting that nobody trusts is usually a data-quality problem. Fixing the source system and the definitions can remove the need for the dashboard project entirely.
- An AI request
- If the underlying process is undefined, a model will automate the confusion. Define the process first, and the model is sometimes no longer required.
- A migration request
- Assessments regularly find applications that should be retired or consolidated rather than moved. Moving fewer things costs less and leaves less to run.
- A rebuild request
- Configuring the existing platform properly, with the governance it never had, is often a fraction of the cost of replacing it.
After go-live
Delivery is the beginning, not the end. Most value is lost in the months after launch, when nobody owns the environment and small problems compound quietly.
Ongoing support covers platform monitoring, application and integration support, data pipeline operations, AI output monitoring, security posture improvement, cost optimisation, backup and resilience oversight, incident coordination and monthly reporting.
Coverage hours, reporting cadence and service levels are agreed per engagement and written into the service description. We do not publish blanket availability or response-time commitments on a web page, because those numbers mean nothing until they are attached to a specific environment and a specific set of systems.
Leadership and team
Founded by three founders, led from Melbourne.
Celestique Cloud delivers through certified cloud consultants holding current Microsoft and AWS certifications, with domain-specific specialisation across AI, data, cloud, security and platform engineering.
Celestique Cloud was founded by three founders and is led from Melbourne. Individual leadership profiles will be published on this page as each one is reviewed and approved. We would rather leave the section short than fill it with biographies that have not been verified, and the same rule applies to photographs.
Every engagement has a named lead who is accountable for it from scope through to handover. You will know who that is before the work starts, and you can ask about the experience behind the recommendation at any point.
Certifications
Stated plainly, and no further.
Our consultants hold current Microsoft and AWS certifications, with domain specialisation across AI, data, cloud, security and platform engineering.
The specific credentials held by the consultants proposed for your engagement are provided on request during scoping, alongside the kind of work each person has done. That is more useful than a badge, because a certification tells you someone passed an exam and not whether they have run your kind of environment.
What we do not claim
- We do not claim Microsoft or AWS partner status, competency or tier.
- We do not publish badge walls, certification counts or how many people hold what.
- We do not hold formal compliance certifications on your behalf, and we do not certify your environment.
- We do not present vendor product icons on this site as evidence of endorsement or affiliation.
Values in practice
Six commitments, and what each one obliges us to do.
Values are only useful if they change a decision. Each of ours maps to something specific that happens, or does not happen, during delivery.
- 01Clarity over complexity
- Plain language in every document, including the ones written for a board and the ones written for engineers.
- 02Outcomes over activity
- Reporting is measured against the success criteria agreed at the start, not against effort spent.
- 03Security by design
- Identity, data handling, logging and guardrails are decided in the design stage, before anything is built.
- 04Practical innovation
- Newer technology is used where it beats the simpler option on evidence, and not because it is newer.
- 05Shared ownership
- Your accounts, your repositories, your documentation. Nothing important is held only by us.
- 06Continuous care
- We stay accountable after go-live, with the scope of that care written into a service description.
Locations and contact
Where we are, and how to reach the right person.
One office, four addresses and a form. Enquiries sent to the wrong address are still answered, they just take a little longer to route.
Contact points
- General enquiries
- info@celestiquecloud.com
- Sales, partnerships and the discovery workshop
- sales@celestiquecloud.com
- Careers
- careers@celestiquecloud.com
- Administration, support and other enquiries
- director@celestiquecloud.com
Melbourne office
Celestique Cloud16 Creek Road
Mitcham VIC 3132
Australia
Meetings are arranged in advance, whether they happen at the office or remotely. Most first conversations are remote, which is usually faster for everyone involved.
Celestique Cloud on LinkedIn(opens in a new tab)Free discovery workshop
See how we work before you commit to anything.
A working session on one real challenge. You leave with an opportunity map, a readiness view and a recommended next step, whether or not it involves us.