01 /Cloud & security
AWS Cloud & Security
Identity, network, data and visibility. Controls built as code, with testing and a clear handover.
Explore cloud & securityAWS cloud · Security · AI
Cloud and AI.
Built for the
real world.
We build, secure and run cloud and AI systems. Practical engineering in your accounts, with the code, controls and handover your team needs.
Your account. Your code. A clear owner from day one.
Engineering, from the inside out.
to production.
Build it. Break it.
Secure it. Run it.
to production.
What we do
The right starting point
for your next step.
Build something new, strengthen what’s running, or give your team the skills to take it forward.
01 /
02 /AI engineering
Gen AI Consulting
Build a scoped AI agent with permissions, evaluation, monitoring and an agreed operating model.
Explore Gen AI consulting
03 /Team capability
AI Training
Hands-on workshops where your engineers build, test and secure an agent, then keep the code.
Explore AI trainingNo feeWell-Architected Review
One AWS workload. Six pillars. A ranked fix list you keep.
Explore the reviewNo feeAWS Cost Review
Read-only analysis. Savings opportunities, with effort and risk.
Explore the cost reviewFree reviews are scoped separately. Any implementation is optional, separately quoted work.
Compare all servicesSelected engineering work
The work behind
the words.
A closer look at the systems, technical decisions and delivery behind our engineering practice.
Our own platform · Built & operated
Automatum.
Engineering we still operate.
Multi-tenant cloud marketplace software, with metered billing and integrations across AWS, Azure and Google Cloud.
Read the Automatum story
AssignarCloud infrastructure for field operations.
Explore the AWS engineering engagement and the context behind the work.
Read the Assignar story
CSIROCloud engineering for research workloads.
Explore the technical challenges and delivery in the CSIRO case study.
Read the CSIRO storyOur engineering approach
Production is
the starting point.
Security, cost and ownership shape the work from the first conversation. We build around the environment your team has to run.
Your repositories. Your infrastructure. Your work.
- 01 /
Build it.
Start with a narrow, useful scope and clear success criteria.
- 02 /
Break it.
Test failure paths and security boundaries within an agreed scope.
- 03 /
Secure it.
Refine permissions, controls and evidence around what the testing finds.
- 04 /
Run it.
Handover, monitoring and a named owner. Ongoing support when agreed.
How we work together
A useful conversation.
A defined next step.
Start with your workload.
Thirty minutes with an engineer to discuss what you need, what’s already running and the constraints that matter.
Agree the work.
Choose the review, build or workshop that fits. Confirm deliverables, timing, ownership and any fee before starting.
Keep what we build.
Findings, code or workshop materials stay with you. Production builds include an agreed handover and operating responsibilities.
What will we have at the end?
Engineering engagements deliver code, controls, test evidence and a runbook. Workshops deliver a repository and learning materials. Free reviews deliver written findings and a ranked plan.
Who owns the work?
Your accounts and repositories. You keep the code, configuration and documentation. We agree any ongoing support or operations separately.
Can you work with our security team?
Yes. We agree the scope, controls and evidence around your review process. Your reviewers and system owners make the approval and deployment decisions.
Is the Well-Architected Review really free?
Yes. tMinus1 pays for the engineering review. You keep the findings whether or not you engage us for implementation. It is not an accredited assessment or certification, and carries no AWS funding.
What happens on the first call?
We discuss your workload, priorities, constraints and the next useful step. If paid work is appropriate, a written quote follows once the scope is clear.
From the engineering desk
Notes from the work.
Your next step
Let’s talk about
what you’re building.
Bring the workload, the challenge or the idea. We’ll work out the next useful step together.
A technical conversation. A written scope before paid work begins.
