Datum Desktop MVP

[bmertens-datum]

Overview

Datum Desktop lets me create tunnels from my laptop into Datum so local services can be reached through the Datum Proxy. This should feel simple and be fast to set up.

The goal is to get from running something on localhost to having a public URL in as few clicks as possible.

Create a tunnel

When I click Create Tunnel, I can: Give the tunnel a name, anything like staging-api or my-laptop Set a local host address, for example http://localhost:3000 or 127.0.0.1:8080 Click Create and be done. All tunnels will be created in the users project by default

Tunnel list

I can see a list of all the tunnels I’ve created. For each tunnel, show:

• Name Local target (host and port)
• The public URL Datum cname and custom hostname if configured
• The Datum Endpoint name
• Traffic inbound and outbound to show the tunnel is working
• links for: Configure DNS and Proxy. Opening a browser and deep linked to the DNS or Proxy config.

Turn on and off

Each tunnel has an obvious toggle. On starts the tunnel Off stops it If something breaks, show a short human readable error like Can’t connect to localhost target. Include a link to view details if needed

Invite a friend

This is nice to have for light collaboration so I can share a tunnel. The invite feature must target a project and organization.

Datum Connect + Desktop Delivery Plan

Goal

Deliver a production-ready Desktop experience that uses Connector/HTTPProxy‑based
routing through Envoy + iroh sidecar, with proper rollout, monitoring, and user UX.

Coordinating , end‑to‑end plan to deliver datum‑connect + datum‑desktop for the
connector-based tunnel flow.

Scope (Initial MVP)

• CONNECT‑TCP only
• Layer 4 advertisements
• Datum Desktop as the initial device agent
• Envoy Gateway integration using one of the three documented approaches

Checklist

• Connector + Envoy design doc Add connector + Envoy design doc #556
• UI initial design for datum‑desktop
• Initial UI implementation for datum‑desktop
  • Auth
  • Tunnel CRUD experience
  • Client side bandwidth charts per tunnel
• Datum Desktop supports Datum auth feat: login to Datum Cloud via the UI app#19
• Datum Desktop leverages Connect/HTTPProxy APIs
  • Connector heartbeat (in-progress)
  • HttpProxy/Connector Advertisements
• Supporting Envoy deployment config
  • Staging
  • Prod
• Iroh gateway implementation and deployment
  • Staging
  • Prod
• Datum Connect controller implementation
  • Connector, Connector Advertisement
  • HttpProxy (in-progress)
• Monitoring/Metrics
• Desktop app is Apple‑signed and hosted for download
  • certificate created
  • stick it in the build ci
• Production rollout and UAT

Dependencies / Links

• Enhancement doc: Add connector + Envoy design doc #556)
• NSO repo/PR:
• Datum Connect repo/PR:

Owners

• Design: @chrisberridge
• Frontend: @mattdjenkinson
• Desktop and Iroh Gateway: @Frando
• Backend/NSO: @zachsmith1 @scotwells
• Infrastructure: @zachsmith1 @scotwells

[drewr]

Quick update here is that we have a working prototype wired up to auth. This has largely fallen on the Iroh team thus far and @zachsmith1 is going to start integrating in earnest on Monday 1/19. We've gotten a big piece merged on our side, which is the Connector resource that will actually facilitate connections. Next up is that we need run the Iroh gateway next to Envoy so that we can terminate connections in Datum Cloud.

[zachsmith1]

I added: https://github.com/datum-cloud/engineering/issues/133

Lets consolidate if needed. @drewr should I move to enhancements or do you want me to update this issue?

[drewr]

Thanks! Let's just keep using this issue so we keep the workstream consistent.