Topic Directory

Content-addressed and peer-distributed storage systems that replace a single provider's disks.

Self-sovereign identity and credentials that don't depend on a single issuing authority.

Running workloads across independently operated machines instead of one cloud provider's datacenters.

Name resolution systems (like ENS or Handshake) not controlled by ICANN-accredited registrars.

Peer-to-peer or federated messaging protocols without one company owning the whole network.

Distributed, multi-writer databases without one operator holding the only copy.

Peer-to-peer file transfer and sync without a central file host.

Wallet-based and cryptographic login flows instead of a central account database.

Peer-to-peer value transfer without a payment processor in the middle.

On-chain voting and proposal systems for collective decision-making.

Getting real-world data onto a blockchain via multiple independent reporters instead of one trusted feed.

On-chain or peer-verified name/asset registries.

Peer-to-peer buying and selling without a platform taking a cut in the middle.

Portable, verifiable track records not owned by one platform.

Token- or credential-gated permissions without a central admin panel.

End-to-end and threshold encryption schemes with no single key holder.

Redundant backups spread across independent peers instead of one provider's snapshot system.

Multi-device or multi-peer data sync without a central sync server.

Indexing and search over peer-distributed content.

Usage and telemetry analysis without one party owning all the data.

Provisioning, monitoring, and maintaining virtual private servers.

Managing bare-metal servers you fully own or lease exclusively.

Configuring content delivery networks to cache and serve assets close to users.

Creating and maintaining the DNS records that point domain names at real infrastructure.

Issuing, renewing, and configuring the certificates that make HTTPS work.

Distributing incoming traffic across multiple backend instances.

Software that sits in front of backend services, routing and terminating traffic on their behalf.

Systems that decide where containers run, keep them running, and reschedule them on failure.

The dominant open-source container orchestration platform and its surrounding ecosystem.

Building, running, and operating Docker containers and images day to day.

Running and operating databases as a service, self-hosted or managed.

Self-hosting SMTP/IMAP mail infrastructure.

Systems and practices for protecting data against loss and restoring it after failure.

Observing system health and capturing logs for debugging and alerting.

Profiling and tuning infrastructure and application performance.

Reducing attack surface and following secure-by-default configuration practices.

Controlling which network traffic is allowed to reach a server.

Automatically adding or removing capacity in response to load.

Automating build, test, and deployment on every code change.

Registering, renewing, and configuring domain names.

Writing, testing, deploying, and auditing on-chain contract code.

Generating, securing, and using cryptocurrency wallet keypairs.

Predicting transaction fees before submitting them on-chain.

Working with fungible/non-fungible token specifications (ERC-20, SPL, etc).

Generating and pinning the JSON metadata standard NFTs point to.

Tracking yields, liquidity, and protocol activity across decentralized finance.

Watching cross-chain bridge activity and security.

Running and maintaining blockchain full nodes or validators.

Browsing and searching on-chain transaction history.

Working with the InterPlanetary File System -- adding, pinning, and retrieving content-addressed files.

Registering and managing Ethereum Name Service domains and records.

On-chain proposal and voting systems for decentralized organizations.

Estimating returns from staking tokens to secure a network.

Optimizing returns across DeFi lending and liquidity protocols.

Requiring multiple signatures to authorize a transaction.

Confirming a message or transaction was really signed by a given key.

Converting between human-readable contract calls and the binary format the EVM expects.

Dry-running a transaction to predict its effects before submitting it.

Reducing the on-chain execution cost of contract code.

"Sign in with wallet" flows using a cryptographic signature instead of a password.

There is no hosted studio. The operator console is served by your own cluster.

Not a separate product: the self-hosting path for Decentralized.Host itself.

Build from source; signed release binaries do not exist yet.

Propose, admit, run, observe, verify.

What Decentralized.Host is appropriate for today.

CLI, manifest, install and operations reference.

Step-by-step walkthroughs taken from the runbooks.

Engineering updates and release notes.

Browse all 69 topic pages in one place.