About tMinus1
Engineers first.Still building.
An AI delivery and training practice in Sydney. We build AI systems, take them to production, and teach your team to run them.
The short version
We learned production by running our own.
We started in 2015, building software products for clients: web, mobile and SaaS. Then we hit a problem of our own. Listing software on the AWS, Azure and Google Cloud marketplaces took an engineering quarter per cloud. So we built Automatum, the platform we wanted, and we still operate it.
That experience is the business now. We do two things: AI delivery, where we build AI systems that pass your security review and stay in production, and AI training, where your engineers learn to build, break and run them. If we recommend something, it is because we have operated it at 2am, not because it was in a whitepaper.
Credentials
Partners who check our work.
We claim engineering. We do not claim to be an accredited assessor of anything. Where you need one, we work alongside yours.
-
AWS Advanced Tier Services Partner
Recognised by AWS for delivering and running workloads on its platform.
-
OpenAI Partner
An OpenAI services partner for building and running AI in production.
-
Certified engineers
The people who build your system hold current platform certifications, including CISSP and AWS Certified Security – Specialty.
That includes our free Well-Architected Review. It is an engineering review by engineers, against the AWS Well-Architected Framework. It is not an accredited assessment, a certification or an audit, and we never present it as one.
The team
The people who build it.
The engineers on your call are the engineers on your project.
Aein Eskandari
Founder & CEO
Hydro Farzad
Head of Cloud Engineering
Jhulio
Cloud Security Engineer
Maryam
AI & Platform Engineer
Leula
Cloud Engineer
Jack
Solutions Architect
How we work
Production is the starting point.
Every engagement follows the same four steps, one use case at a time.
- 01
Build it.
Around a real workflow, in your accounts and repositories.
- 02
Break it.
Test the failure paths before anyone else finds them.
- 03
Secure it.
Permissions, guardrails and the evidence your security team asks for.
- 04
Run it.
Monitoring, a runbook, and a team that knows how to keep it going.
- A written scope before paid work begins.
- Everything lands in your accounts and your repositories.
- If you stop working with us, you keep the system, the runbook and the evidence.
Next
Talk to the people who run it.
Request a technical callThirty minutes with an engineer, not a salesperson.