Coming Soon #

Services that are designed — each has an architecture decision record — but not built. Nothing here can be declared today. The shape described is the proposal’s, and may change before it ships.

Secrets #

Today: anything secret your application needs lives in your Terraform state or your own tooling. Planned: a namespace of your own in the platform secrets store, holding a runtime copy of secrets your repository owns, written through the API, and read by your workloads with their own identity. ADR-0021

Metrics and alerting #

Today: logs are the only telemetry the platform stores for you, though a numeric field in a device’s JSON log line can already be graphed. Planned: your workloads push metrics into a partition of your own (the platform never scrapes a tenant workload), you declare alert rules that run under your own token, and notifications go out through a platform push service. Your Grafana organization gains metrics data sources beside the log ones. ADR-0023

Identity #

Today: the API token is your tenant’s identity; there are no user accounts. Planned: a realm of your own in a platform identity directory, for your application’s users and for SSH to your workloads by short-lived certificate. ADR-0025

Object storage #

Today: the state store holds Terraform state only. Planned: S3-compatible buckets of your own for application data, declared like everything else. ADR-0026

Code delivery to workloads #

Today: a workload boots Fedora with nothing of yours on it, and — because ssh_keys is broken — the operator installs your code for you. Planned: a workload fetches a Deevnet-shaped description of what to run at boot, so declaring the workload is enough to have it running your code. ADR-0017

A tenant devbox #

Today: you install the tools on your own laptop, with the provider and the large downloads served by the site. Planned: a development workload, built from an image with the tools already on it, that you launch in your own tenant network, so the Terraform and CLI half needs nothing on your laptop. Flashing a device or an SD card still needs your laptop’s USB. It waits on ssh_keys and on code delivery.