Terminal when you need it.
Clear controls when you do not.
Start with the safest interface for the job, then move into the shell without changing context.
Direct SSH, practical server controls, and optional AI assistance in one focused app. Preview the command, understand the risk, then decide what runs.
PRODUCTION / PRIMARY
Upstream service stopped after a memory limit was reached. I found one safe recovery action.
sudo systemctl restart node-apiRestarts the failed service. No files or configuration will be changed.
Works with the infrastructure you already run
One control plane
Use direct controls when the task is familiar. Ask the assistant when it is not. Drop into a full terminal whenever you need exact control.
QUICK ACTIONS
deploy@prod-api-03:~$ uptime
15:42:08 up 31 days, 4:18, 1 user, load average: 0.72, 0.69, 0.58
deploy@prod-api-03:~$ systemctl status node-api --no-pager
● node-api.service — Node API
Loaded: loaded (/etc/systemd/system/node-api.service; enabled)
Active: active (running) since Sat 2026-07-04 15:39:11 UTC
deploy@prod-api-03:~$
Human in the loop, by design
AI helps prepare the work. You stay responsible for execution.
Choose a saved server. HAMMA opens SSH from your device—there is no proxy in the middle.
Pick an action or explain what is wrong in plain language. The terminal remains available.
See every proposed command, what it changes, and a clear risk classification.
Run, edit, or reject. Output and the local audit trail reflect what actually happened.
Built for the whole operation
HAMMA combines the practical tools used in day-to-day server management without hiding the underlying system.
Start with the safest interface for the job, then move into the shell without changing context.
Save multi-step command sequences, review each stage, and reuse the workflow when the same problem returns.
Use Ollama, LM Studio, llama.cpp, or an explicitly configured hosted model. AI is modular; SSH is not dependent on it.
Local-first architecture
Direct SSH remains between your device and your server. Credentials are stored in the encrypted local vault. When Local AI is selected, model traffic is restricted to loopback addresses.
AES-256-GCM vault with Argon2id key derivation.
SSH goes from the app to your host, not through HAMMA infrastructure.
AI-generated commands are shown and confirmed before they run.
Cloud AI is optional and separately configured. It is never the SSH transport layer.
A different system boundary
HAMMA is built around device-to-server SSH. That architectural choice changes what the product needs to know about your infrastructure.
Comparison describes common managed architectures; individual vendor behavior varies by product and configuration.
Designed for responsible operators
SOLO OPERATORS
Move from symptom to a reviewed command without opening six tools or pasting sensitive logs into a random chat.
SMALL TEAMS
Save runbooks, share a clear workflow, and keep raw terminal access available for the people who need it.
RESTRICTED NETWORKS
Use direct SSH and local inference in environments where production data cannot be sent to a hosted model.
Straight answers
HAMMA is a beta release candidate and is free to inspect, download, and use.
No. The core connection is made directly from the Flutter app to the server using SSH.
Yes. Server profiles, SSH, terminal access, quick actions, and file operations do not require an AI provider.
No. Commands are visible before execution and require confirmation. Risky operations receive stronger warnings.
HAMMA targets Linux, Windows, macOS, Android, and iOS from the same Flutter codebase.