AgentAura

What is AgentAura?

AgentAura installs and connects a supported AI-agent runtime. The current Web flow is bring-your-own-server (BYOS): you create and administer a compatible public Linux server and provide administrator SSH access. Some native builds and accounts may instead show a managed provider-account flow that uses cloud credentials you supply to create resources in your own cloud account. Available flows, providers, plans and regions are only those shown in the current app.

Key Benefits

• 🧭 Guided runtime installation — connection checks and guided setup for the deployment path shown in your client
• 💬 Supported chat clients — connect to the installed agent from supported AgentAura clients
• 🖥️ Current Web BYOS — choose and prepare the host, size and region directly with the hosting provider
• ☁️ Conditional native managed flow — some native builds and accounts can create resources in your cloud account using credentials you provide
• 🔑 Bring your own AI key — model availability, billing and data handling depend on the provider you configure
• 🔒 Clear control boundaries — you administer the host, SSH access, operating system, firewall, updates and backups
• 💾 Optional backup configuration — connect supported storage when you want an additional copy of eligible runtime data

Current Web BYOS Flow

1. Prepare a server — create a compatible public Linux server with your host and keep administrator SSH credentials ready
2. Download and sign in — install AgentAura and complete any account verification shown in the current client
3. Add your server and model credentials — AgentAura checks the connection to the server you supplied
4. Install the runtime — follow the guided installation and health checks; duration depends on the server and network and is not guaranteed
5. Connect and maintain — use supported clients for the agent while continuing to manage the server through your host

AgentAura does not take a cloud-provider provisioning token in the current Web flow, choose a hosting plan or region for you, or create, stop, restart, cancel or destroy the BYOS host server.

Native Managed Provider-Account Flow

Some native builds and accounts may show a separate managed deployment option. In that path, AgentAura uses cloud credentials you provide to create resources in your cloud account and can expose management or deletion controls for resources that path created. Provider, plan, region and lifecycle options depend on the current app and account. Review every confirmation and verify the resulting resource and billing state in the provider's console; no provider count or completion time is promised.

Plans

Features

💬 Supported chat clients

Connect to the installed agent from supported AgentAura clients. Available chat, rendering, session and control-panel features depend on the client and runtime version.

🔑 Bring your own AI model

Configure a model provider supported by the current runtime. That provider bills model usage and may process prompts, responses and related metadata under its own terms.

🖥️ Bring your own server

Prepare a compatible public Linux server with administrator SSH access. You choose and pay the hosting provider directly; server availability, isolation and security depend on your host and configuration.

☁️ Conditional native managed deployment

Where the current native app and account offer it, you can authorize a displayed provider-account flow to create resources in your own cloud account. Use only the providers, plans and regions shown there, grant the narrowest practical cloud permissions, and verify billing and deletion in the provider console.

🔒 Privacy and provider boundaries

The agent runtime runs on the server you administer, but self-hosting does not make every data flow local. AgentAura platform services can participate in account, installation and connection flows. Your host, selected AI provider, storage provider and enabled integrations may process data sent to them under their own terms.

💾 Optional backups

Where supported, configure storage you control to back up eligible runtime data. Backup coverage, retention and restoration depend on your runtime, storage and configuration; verify a restore before relying on it.

🎛️ Separate runtime and host controls

For Web BYOS, AgentAura can manage supported runtime operations, but removing an agent or runtime does not cancel, erase or destroy the underlying server. Use your hosting provider to manage that server's billing, security, operating system, storage and lifecycle. A native managed provider-account path may offer controls for resources it created; read the deletion confirmation and verify the outcome and billing state with the provider.

Supported Platforms

Getting Started

Technical Boundaries

In Web BYOS, AgentAura installs supported runtime components on the compatible server you provide and connects supported clients through the configured gateway. You retain administrator access and responsibility for that host. In an available native managed provider-account flow, resource creation and lifecycle controls depend on the current app, account and cloud provider. Access, encryption and isolation depend on the runtime version, your configuration and the providers involved.

For Web BYOS, you provide and manage:

• A compatible public Linux server and administrator SSH credentials
• The hosting account, server billing, firewall, updates, storage and lifecycle
• Credentials for a supported AI model provider
• Any optional storage or integration providers you enable

---