Skip to main content
After your DePIN is integrated with the peaq network, with machine wallets, DIDs, and verifiable data flows in place, the next step is to decide how your users or devices interact with the system in production. There are several common deployment models depending on your use case, each with its own strengths:
  • Server Implementation
  • Mobile Application
  • Web Application
Below is a high-level overview of how each approach works and what makes it unique. These models can also be combined depending on your architecture.

​
Server Implementation

A server-side deployment is the most flexible and common approach for DePINs, especially when dealing with multiple machines, background processes, or integrations with legacy infrastructure.

​
Key Characteristics

  • Control of DID creation, wallet generation, and on-chain transactions.
  • Ideal for IoT networks, machine fleets, or backend-only services.
  • Can be scheduled, event-driven, or triggered via APIs from other systems.

​
Typical Use Cases

  • Creating a machine DID as soon as a new device is provisioned.
  • Running cron jobs or real-time services to monitor machine behavior and update DIDs.
  • Hosting APIs that allow frontends (web/mobile) to interact with blockchain logic securely.

​
Tech Stack

  • Node.js, Python, or Go backend
  • Cloud infrastructure (AWS, GCP, Azure)
  • Secure key management (e.g. HSMs, Vault, KMS)
Recommended when you need maximum control and scalability across a large number of machines or services.

​
Mobile Application

A mobile-based DePIN enables end-users to manage their machine identities or interact with the network directly from their smartphone.

​
Key Characteristics

  • Local wallet generation and signing using device secure storage (e.g. Keychain, Keystore).
  • Direct integration with peaq DID SDK and peaq storage via lightweight APIs.
  • Enables machines controlled or managed via phones (e.g. mobility services, consumer DePINs).
  • Integration with Account Abstraction solutions.

​
Typical Use Cases

  • End-user onboarding flow to create a machine wallet and DID when setting up a device.
  • Enabling rideshare drivers, delivery partners, or remote workers to verify data from their device.
  • QR code scanning or Bluetooth-triggered DID operations.

​
Tech Stack

  • React Native, Flutter, or native iOS/Android
  • Lightweight backend for transaction relaying (optional)
  • Integration with WalletConnect, push notifications, or secure enclave features
Recommended for DePINs targeting individual users, decentralized access, or mobile-first ecosystems.

​
Web Application

A web app-based DePIN allows machines or users to interact with the peaq network through a browser interface, offering a lightweight and accessible entry point.

​
Key Characteristics:

  • On-demand wallet generation using browser-based tools (e.g. ethers.js, @peaq-network/sdk).
  • Great for dashboard-style tools, data viewers, or admin portals.
  • Ideal for browser-based configuration or onboarding flows.
  • Integration with Account Abstraction solutions.

​
Typical Use Cases:

  • Admin portals that manage a fleet of machines via a web dashboard.
  • Frontend tools that allow users to submit or verify data tied to machine DIDs.
  • Public explorers, visualizations, or analytics for DePIN networks.

​
Tech Stack:

  • React, Next.js, or Vue.js frontend
  • SDK integration for DID operations and storage writes
  • Optional backend for signing or relaying if key custody is needed
Recommended for data transparency, interactive dashboards, or lightweight onboarding experiences.

​
Choosing the Right Approach

Each deployment method is valid and can be adapted to your specific needs. In many cases, projects combine two or more approaches. For example:
  • A server handles DID creation and background processes.
  • A web app provides admin controls.
  • A mobile app allows users to interact directly with machines.
Once you’ve chosen your approach, continue to the Pre-deployment Checklist below to ensure a smooth launch to peaq mainnet.

​
Pre-deployment Checklist

​
Security audits

Audit the smart contracts and DID implementation before you deploy to peaq mainnet, and stress test them under mainnet conditions.

​
Monitoring and analytics

Set up monitoring and blockchain analytics to track transaction volume, contract activity, and unusual patterns after launch.

​
Documentation and tutorials

Publish step-by-step guides and developer tutorials for interacting with your DIDs, smart contracts, and token.

​
Incentive programs

Run a bug bounty so security researchers have a reason to report vulnerabilities, and consider rewards for early adopters who test the system.

​
Governance and tokenomics

Publish your governance and token details, including staking, voting, and reward structures, so users know how to participate.

​
Community and developer engagement

Host an AMA or community event around the launch to answer questions about functionality, vision, and roadmap.

​
Integration announcements

Announce the collaborations and ecosystem integrations that go live alongside your deployment.

​
Post-launch support

Share your post-launch roadmap and set up support channels: help desks, community moderators, or a support email.

​
Compliance

Confirm the deployment complies with the laws and regulations that apply to you, and state which frameworks you follow.

​
User education

Run education campaigns such as webinars, videos, and blog posts so end users understand how to use what you deployed.