Platforms and deployment
Programs written in AEL, the Agent Engineering Language, compile straight to self-contained native executables, with no interpreter or virtual machine to run and no second language to install unless you write functions in one. One language reaches from servers down to microcontrollers, and a feature a target cannot support fails at compile time, not on the device.
This section describes the targets, what a program looks like on each of them, and how you deploy, watch and roll back what you build.
The targets at a glance
AEL 1.0.0 builds for these targets:
| Where it runs | What you build | Read more |
|---|---|---|
| Linux, macOS and Windows | A native executable for one operating system and processor. | Desktop and server |
| Containers | Static Linux executables and minimal container images for x86-64 and ARM64. | Containers |
| Microcontroller boards | A firmware image, with RAM, flash and stack reports, that you flash and monitor from the command line. | Microcontroller boards |
The exact operating systems, processors and boards are listed under Supported targets. Runtimes come in sizes for each class of device, from servers down to coin-cell-class microcontrollers, and a program that does not fit its device's class is refused when you build it.
AEL 1.0.0 is the full distribution; smaller distributions of the same version leave out components, such as support for other languages or for agents, and refuse a feature they leave out by naming it. Distributions describes them.
In this section
- Supported targets: the exact targets of AEL 1.0.0, their target names and profiles, and where isolation and the sandbox run.
- Desktop and server: native executables for Linux, macOS and Windows, static Linux executables, the runtime, resource limits and source-level debugging.
- Microcontroller boards: firmware images and memory reports, runtime sizes, hardware access, robotics device packages, flashing and monitoring, and prompt-driven agents through AEL Gateway.
- Containers: minimal container images that start with nothing to compile, install or download at startup.
- Self-hosting your application: your built application on servers you operate, with health checks for the storage, databases and models it declares, graceful shutdown and log rotation.
- Deployment and rollback: reviewed deployment plans, staged activation and rollback.
- Logging and monitoring: where logs go on each kind of target, health and readiness, resource use and watching a device.