The Dilmune platform

Your stack.
All together.

Servers, sites, edge functions, databases and storage. One workspace, with Muno, your AI assistant.

01Servers

Your servers. Still yours.

Provision and manage servers across your cloud providers, with SSH access intact.

Your cloud, connectedChoose a provider
Dilmune

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
Interactive illustration · no cloud account connected
02Sites

Ship forward. Roll back.

Deploy from Git to your server, with automatic TLS. Restore an earlier commit and keep your deployment history.

DeploymentsGit → your server
Live

example.com

Update homepage

#42 · 8e4b2c1

  1. #42

    8e4b2c1

    Current release

Current live deployment and preserved release history.

Restore an earlier release.

  1. Queue, waiting
  2. Build, waiting
  3. Deploy, waiting
  4. 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

  1. No rollback requested.
Interactive sample · no real server changes
03Apps

Code to endpoint. No server needed.

Run edge functions without managing a server. Test a request, then call the same endpoint from your app.

Request in. Response out.Edge functions
Send
Edge function
200OK
Response
application/json
{ "status": "ok" }
Try a request

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" }
Interactive sample · no network requests
04Databases

Query your data. See the answer.

Run SQL and inspect results without leaving the dashboard. Connect with your own database tools whenever you want.

Select a record to inspect it.Database queries
appdb3 matches
Selected recordIncluded
name
website
status
active
Choose a query

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;"
Interactive sample · local, read-only data
05Storage

Your files. Your familiar tools.

Browse files and preview images. Use the same bucket with your S3-compatible tools.

assets /3 example objects
Pick a file to inspect

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.

06Operations

CPU and memory. Over time.

Follow your server’s resource usage. Switch metrics and inspect individual readings to see what changed and when.

web-01Last hour · sample data
Metric to inspect

24%

CPU
Now

1h agoNow
CPU is now 24%, down from a 72% peak in this example.

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%
07Muno

Ask Muno. Keep the final say.

Ask about your infrastructure. Review the target and impact before approving actions like a server reboot.

MunoYou decide what runs

Reboot web-01

One server. Offline while it restarts.

Muno

Proposes

You

Approval needed

web-01

Unchanged

Nothing has run. Your approval is needed first.

See the request trace

Illustrative trace · no real request is sent

Proposal: reboot_server
Target: web-01
Approval: waiting
Reboot request: not sent
Interactive sample · no real server changes

Make it yours.

Start with a server, an app, or a bucket. Find the plan that fits what you’re building.