Version 1.1: Introducing awaBerry Agentic

awaBerry Agentic 1.1 introduces a web-based project management interface with API Key and Password authentication, enabling secure programmatic access to your devices through the awaBerry API.

We are excited to announce awaBerry Agentic 1.1, the first release of a product line that will define how developers and operations teams interact with their device fleets programmatically. Today's release establishes the core building blocks: projects, credentials, and secure API-based device connectivity.

Projects and API Credentials

The new awaBerry Agentic web interface allows you to create and manage projects. Each project receives a unique API Key and Password — the two credentials that identify and authorise your application when communicating with the awaBerry API.

This credential model is deliberately simple and portable. Whether you are writing a Python script, a Node.js service, or a GitHub Actions workflow, integrating with awaBerry Agentic is a matter of setting two environment variables and making standard HTTPS requests.

Secure Device Connectivity via the awaBerry API

Once authenticated, your application can reach any device registered under the project through the awaBerry API. Commands are executed on the device via a dedicated non-root user — awaberry — that is created automatically during agent installation.

Running as a dedicated, non-root user means that API-driven operations are isolated from the rest of the system by default. Privilege escalation is explicit and auditable, not implicit. This is the kind of defence-in-depth that modern DevOps and security teams expect as a baseline.

What You Can Build With It

awaBerry Agentic 1.1 opens up a wide range of integration scenarios:

Automated health checks and monitoring pipelines
Remote configuration and software deployment scripts
CI/CD hooks that trigger device-side actions on code push
Custom dashboards that query device state in real time

API Documentation

Full API reference documentation is available in the User Manual. We have included code examples for the most common integration patterns. If you have questions or feedback on the API design, please reach out via our contact form — we are actively shaping the roadmap based on developer input.