The Dilmune platform
Your stack.
All together.
Servers, sites, edge functions, databases and storage. One workspace, with Muno, your AI assistant.
Your servers. Still yours.
Provision and manage servers across your cloud providers, with SSH access intact.
Hetzner. Your account.
Dilmune manages it. You keep the keys.
Connect with SSH
Sample connection · your deploy user has sudo access
$ ssh -l dilmune 192.0.2.10 dilmune@web-01:~$ sudo -i root@web-01:~# whoami root
Ship forward. Roll back.
Deploy from Git to your server, with automatic TLS. Restore an earlier commit and keep your deployment history.
example.com
Update homepage
#42 · 8e4b2c1
#42
8e4b2c1
Current release
Restore an earlier release.
- Queue, waiting
- Build, waiting
- Deploy, waiting
- Live, waiting
The current release stays live while the new one builds.
Try a sample rollback. Your site stays live and deployment history is preserved.
View deployment log
Illustrative log · timing shortened
- No rollback requested.
Code to endpoint. No server needed.
Run edge functions without managing a server. Test a request, then call the same endpoint from your app.
{ "status": "ok" }GET /health: 200 OK. { "status": "ok" }
Same request with curl
curl -i 'https://health.fn.dilmune.app/health'
HTTP/2 200
content-type: application/json
{ "status": "ok" }Query your data. See the answer.
Run SQL and inspect results without leaving the dashboard. Connect with your own database tools whenever you want.
- name
- website
- status
- active
All projects: 3 matching records. website, active. api, active. docs, archived. Inspecting website, active. Included in the current query.
See the SQL query
SELECT name, status
FROM projects;
name status
──────────────────
website active
api active
docs archived
(3 rows)Same query from your server with psql:
psql -h localhost -p 5432 -U appdb_admin -d appdb -c "SELECT name, status FROM projects;"
Your files. Your familiar tools.
Browse files and preview images. Use the same bucket with your S3-compatible tools.
dilmune.png
image/png · 255 KB
Use this file with AWS CLI
aws s3 cp 's3://assets/dilmune.png' . --endpoint-url 'https://api.dilmune.com/s3'
Example bucket and key. Configure your own S3 credentials before using the command with your files.
CPU and memory. Over time.
Follow your server’s resource usage. Switch metrics and inspect individual readings to see what changed and when.
24%
CPU
Now
CPU 24% at Now. CPU is now 24%, down from a 72% peak in this example.
Inspect the sample values
CPU usage · five-minute samples
- 60m ago
- 18%
- 55m ago
- 22%
- 50m ago
- 19%
- 45m ago
- 31%
- 40m ago
- 25%
- 35m ago
- 38%
- 30m ago
- 72%
- 25m ago
- 54%
- 20m ago
- 39%
- 15m ago
- 44%
- 10m ago
- 32%
- 5m ago
- 28%
- Now
- 24%
Ask Muno. Keep the final say.
Ask about your infrastructure. Review the target and impact before approving actions like a server reboot.
Reboot web-01
One server. Offline while it restarts.
Muno
Proposes
You
Approval needed
web-01
Unchanged
See the request trace
Illustrative trace · no real request is sent
Proposal: reboot_server Target: web-01 Approval: waiting Reboot request: not sent
Make it yours.
Start with a server, an app, or a bucket. Find the plan that fits what you’re building.