AgentAura FAQ
Frequently asked questions about AgentAura's bring-your-own-server installation flow, billing and data boundaries.
Frequently Asked Questions
General
What is AgentAura?
AgentAura installs and connects a supported AI-agent runtime. The current Web flow is bring-your-own-server (BYOS): you first create a compatible public Linux server and obtain administrator SSH access. Some native builds and accounts may instead offer a managed provider-account flow that uses cloud credentials you supply to create resources in your own cloud account.
Does AgentAura create or sell the server?
Not in the current Web flow: Web does not accept a cloud-provider provisioning token, select a hosting plan or region, or create, stop, restart, cancel or destroy a BYOS server. Some native builds and accounts may show a separate managed provider-account flow. That flow can create resources in your cloud account using credentials you provide and expose controls for resources it created. Only rely on the options and confirmations shown in the current app, then verify the resource and billing state with the provider.
How is this different from a hosted AI app?
The supported agent runtime is installed on a server you administer and uses the model provider you configure. You remain responsible for the host, while AgentAura platform services can participate in account, installation and connection flows. It is not accurate to assume that every data flow stays only on the server.
Is my data private?
Privacy depends on the feature and configuration. Your host can process infrastructure and network data. Your selected AI provider processes model requests, and storage or integration providers can process data you send to them. Protect SSH and account credentials, restrict network and tool permissions, apply updates and review each provider's terms before sending sensitive data.
Billing & Subscriptions
How does pricing work?
There are separate costs:
- Hosting costs — billed directly by your hosting provider and dependent on the server, region, storage, traffic and taxes.
- AgentAura subscription — Free includes 1 agent. Web/Stripe Pro is $4.99/month or $47.88/year and permits up to 50 agents per account; capacity and fair-use limits apply. App-store pricing may differ (currently $4.99/month or $49.99/year). The checkout or purchase sheet controls the final price, billing period and included platform features.
- AI and optional provider costs — model, storage and integration providers can bill you separately under their own terms.
AgentAura does not resell the host server or AI tokens.
Can I cancel anytime?
Manage and cancel the subscription through its original purchase channel. Cancellation does not cancel or delete the server in your hosting account; continue to manage that server and its charges directly with the host. AgentAura feature access after cancellation follows the entitlement shown by the purchase channel and current product.
Server & Hosting
Which hosting providers can I use?
For Web BYOS, use a host where you can create a compatible public Linux server and obtain the required administrator SSH access. For a native managed provider-account flow, available providers are only those displayed for the current build and account. AgentAura does not promise a provider count; check the current client before buying a host.
Can I choose the server location and size?
For Web BYOS, choose them in the hosting provider's own console before adding the server. A native managed provider-account flow may show plan and region choices in the app; availability depends on the current build, account and provider.
How long does installation take?
There is no guaranteed completion time. Connection checks, package downloads, runtime installation and health checks depend on the server, package sources and network. A failed or interrupted install does not cancel the server or stop hosting charges.
What does deleting an agent do?
For Web BYOS, removing an agent affects only the AgentAura agent or runtime state covered by that control; it does not cancel, erase or destroy the underlying server. A native managed provider-account flow may offer deletion for resources it created. Read the exact confirmation, then verify deletion, storage and billing state in the cloud provider's console.
AI Model
Which AI models can I use?
Use a model provider and model supported by the current AgentAura runtime. Availability can change by runtime version and provider. The provider bills usage and processes prompts, responses and related metadata under its own terms.
Where are my model credentials stored?
Credential handling depends on the current client, platform services and installed runtime. Protect and rotate credentials, grant only the required scope, and review the privacy policy and provider documentation. Do not assume credentials or requests are processed only on your server unless the current implementation and provider terms explicitly confirm it.
Data & Backup
Can I back up my agent's data?
Where supported, you can configure compatible storage for eligible runtime data. Backups are not automatic merely because a server is connected. Coverage, retention and restoration depend on the runtime, storage provider and your configuration; test a restore before relying on it.
Devices
Which platforms are supported?
Current download options include iOS, Android, macOS, Windows, Linux, Web and Chrome clients. Feature availability can differ by client and version.
Troubleshooting
The agent runtime shows "Stopped"
Check the runtime controls available in AgentAura and confirm that the host server itself is online. If the host is stopped, unreachable or misconfigured, manage it through the hosting provider.
Runtime installation failed
- Confirm that the existing server is online and publicly reachable
- Verify the hostname or IP address and administrator SSH credentials
- Check supported Linux prerequisites, firewall rules and package access
- Confirm the selected AI provider credentials when that stage is reached
- Review the installation output and retry, or contact support
AgentAura does not need a cloud-provider provisioning token for the current Web BYOS flow. A native managed provider-account flow may request cloud credentials for a provider displayed in that app.
Can't connect or chat isn't working
- Confirm that both the host server and installed runtime are healthy
- Check the model provider credentials and provider status
- Review firewall, gateway, account and device authentication settings
- Check any enabled storage or integration provider
- Contact support if the issue persists
Still have questions? Contact support@allianceinterstellar.com