PowerCloudRoadmap
Built, and next
PowerCloud is early. This is the roadmap, area by area: what is built and working today, and what is planned next. Nothing planned is described anywhere on this site as working.
- 01
Storage core
5 built
- ✓Key hierarchy with passphrase and recovery-key slots
- ✓Encrypted, deduplicating object store
- ✓Replication across providers
- ✓pcctl, and pcinit with its supervisor
- ✓Initramfs builder
- 02
Boot
9 built, 1 planned
- ✓Hardened Linux kernel config
- ✓QEMU boot self-test in CI for amd64 and arm64
- ✓Bootable UEFI disk images with a built-in initramfs and locked command line
- ✓Secure Boot with your own key
- ✓Built-in drivers for AWS, Google Cloud, Azure, VMware and physical servers
- ✓AWS: AMI upload, boots on x86 and Graviton, Secure Boot and NitroTPM unlock
- ✓A/B upgrades with a trial boot and automatic rollback
- ✓Signed releases that nodes roll out themselves, one at a time
- ✓Google Cloud and Azure image formats
- Booting on Google Cloud and Azure Planned
- 03
Nodes
9 built
- ✓Node identity, console enrollment codes and an mTLS node API with roles
- ✓WireGuard mesh with identity-derived addresses and peer health
- ✓CA-signed membership list gossiped over the mesh
- ✓NAT traversal through peers, and relays for symmetric NAT
- ✓Node removal, revocation spread over the mesh, crypto-erase
- ✓Certificate renewal, including for expired nodes
- ✓Unattended join from cloud user data or QEMU fw_cfg
- ✓Cluster key rotation
- ✓Nodes serving the storage to admins
- 04
Unlock
4 built, 2 planned
- ✓Encrypted state volume with admin-approved unlock after reboot
- ✓TPM 2.0 unlock sealed to the Secure Boot state
- ✓Authenticated disk encryption (dm-integrity, HMAC-SHA256)
- ✓Attested unlock on AMD SEV-SNP VMs
- Peer unlock with Shamir shares Planned
- Intel TDX and Arm CCA attestation Planned
- 05
Backends
5 built
- ✓S3-compatible: AWS, R2, B2, Wasabi, MinIO
- ✓check, repair and gc
- ✓Nodes' disks as storage locations
- ✓Scheduled sync of missing blobs
- ✓Erasure coding instead of full replicas
- 06
Cluster
8 built, 1 planned
- ✓Cluster-wide app placement from CA-signed documents
- ✓App data on encrypted node volumes
- ✓A Raft group among the nodes with replicated state
- ✓Exclusive apps with fencing
- ✓Rollback protection through the nodes' consensus
- ✓App volumes that follow exclusive apps
- ✓Linearizable reads of the consensus state
- ✓Placement within each node's memory
- CPU in placement Planned
- 07
Compute
4 built, 3 planned
- ✓Sandboxed apps: namespaces, chroot, cgroup limits, seccomp, own network
- ✓Container images from registries, private ones included
- ✓Cluster apps placed by the nodes, with failover
- ✓App storage: an S3 endpoint per app over the encrypted storage
- MicroVMs Planned
- S3-compatible gateway Planned
- Web console Planned
Follow along
The roadmap moves with the code, and this page with it. There are no builds to download yet.