GLWS · AI agents
An agent workspace for conversations, tools and automation on infrastructure you control.
Common uses of Hermes Agent.
Model providers can have separate usage costs. Keep API credentials outside public files and use restricted credentials when available.
Planning examples, not official minimum requirements.
AI agents
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the Hermes Agent documentation ↗ (opens in a new tab)Advice specific to this application.
An agent workflow can involve a model endpoint, local tools and scheduled activity. List each component and the data it can read or change. Evaluate the complete workflow when choosing resources, including any browser or command-line work it triggers.
Store configuration and workflow notes outside the agent environment. Track the credentials supplied to tools so each can be rotated independently. Repeated jobs should have a clear owner and a way to stop them without depending on an unfinished conversation.
Linux guides that help with this setup.
Install Hermes Agent, choose a model, connect a messaging gateway, run it as a boot-time service and control who is allowed to use it.
Read guide →Keep AI services off the open internet: bind to localhost, avoid the Docker firewall bypass, add authentication and verify from outside.
Read guide →Keep API keys out of code, load them through systemd, set timeouts, retries and spending limits, and rotate a key that leaks.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name hermes-agent
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →Website, email, DNS and database management in a hosting dashboard.
Explore application →Connect services and build repeatable workflows with a self-hosted automation platform.
Explore application →Organise document-centred AI conversations and connect the model backend that suits your project.
Explore application →