A local cluster that behaves like the one you deploy to.
Imagine opening your project in a browser at a real address such as portal.dev.mycompany.io, with a padlock and no warnings, while everything runs on your own computer. That is what AIDE sets up. You describe the project in one small file, and AIDE builds a private cluster for it, gives it web addresses under your own domain and makes your computer trust its certificates.
When you want to change a service, you do not have to rebuild anything. AIDE can point that service at the program you are editing on your machine. The address and the padlock stay the same, and your edits show up as soon as you reload the page. When you are done, one step sends it back to the cluster.
AIDE prepares the environment. You or your coding agent put the application in it and check that the address works.
What you gain over a port number on localhost.
A plain local address skips the web address, the padlock and the routing you meet in a real deployment, so those problems show up late. AIDE keeps them in the picture from the first day.
Real addresses and HTTPS
You test with the same kind of address you will deploy to
- Typical alternative
- A local setup reached through port numbers, with no project domain and no trusted certificate
- Here
- Your project gets proper web addresses under your own domain, secured with a certificate
Edit a running service live
Your edits appear on reload, with no image rebuild
- Typical alternative
- A tunnel that bypasses the real entry point
- Here
- One service can be pointed at the program on your machine while the address and certificate stay as they are
Trust is set up for you
The padlock is genuine, and you never switch certificate checks off
- Typical alternative
- Clicking through browser warnings or installing a certificate by hand
- Here
- The project's certificate is made trusted on your computer, and in browsers where possible
Works offline most of the time
A dropped connection does not interrupt your work
- Typical alternative
- A tool that asks an online account service on every command
- Here
- Your access is checked on your own computer, so a working session carries on without a connection until renewal is due
A ready briefing for your agent
The agent starts informed instead of exploring by trial and error
- Typical alternative
- Describing the cluster to an agent by hand
- Here
- AIDE writes out your project's domain, cluster access and routing rules in words the agent can follow
Clear state and checks
You find the failing part before you change anything
- Typical alternative
- Guessing why an address does not work
- Here
- AIDE reports what is running, what is redirected and which part of your setup is missing
Installed with one command, run inside your project.
The MAIT image includes AIDE. Anywhere else, install it with one aidc command (aidc install mait:aide@latest). It needs Docker and an account that includes the local cluster feature. A one-time setup step then installs the few helper tools it uses. After that, everyday commands keep working without a network connection until your access is due for renewal.
Where it sits in the MAIT toolkit.
Where to read on.
- Install, then Workflows
- Operate and Customize
- What AIDE changes, for what it changes on your machine