OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Wallets

Opensigner

An open-source, self-hostable service for vendor-neutral, non-custodial key management for embedded wallets.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Opensigner — OpenViST project profile in Wallets.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when an application needs self-hosted, non-custodial wallet infrastructure and wants its existing authentication system to remain the user-facing entry point.

Who it is for

  • Teams building consumer crypto applications with embedded wallets.
  • Developers deploying wallet key-management infrastructure on their own systems.
  • Security and engineering teams reviewing an open implementation and deployment model.
  • Applications using Ethereum or Solana that want to connect wallets to existing authentication.

Documented uses

  • Create embedded non-custodial wallets for application users.
  • Store and recover split key shares across device, hot and cold storage.
  • Reconstruct keys temporarily in memory for signing.
  • Connect existing authentication flows to wallet creation and use.
  • Separate wallet key management from a specific wallet infrastructure provider.
Before you choose

Requirements & limits

The repository is public, open-source and MIT-licensed. The documented deployment is self-hosted and uses Docker Compose; no account or pricing requirements are documented in the supplied material.

  • Self-hosting is central to the project’s deployment model.
  • Key shares are divided into device, hot and cold shares using Shamir’s Secret Sharing.
  • The documented authentication integrations include OIDC, passkeys and email flows.
  • Ethereum and Solana are explicitly identified as supported ecosystems.
  • The setup requires manually populated secrets before the Compose stack can start.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Run the Opensigner stack locally

Prepare and start the documented Docker Compose stack for local use.

Before you start

  • A cloned copy of the Opensigner repository.
  • Required secret values populated in a .env file.
  • Docker Compose and the project build tooling used by the repository.

Steps

  1. Clone the repository and change into its directory.

  2. Copy .env.example to .env and fill in every required value.

  3. Set database passwords before the first start, because PostgreSQL fixes them when the data volume is first created.

  4. Build the project with make build.

  5. Run the full stack with make run.

Expected outcome

The documented local stack starts with iframe, sample page, authentication, hot-storage and cold-storage services exposed on their listed default ports.

Guide limitations

  • The repository does not provide defaults for required secrets.
  • Changing database passwords after the initial volume is created does not update that existing volume.
  • make clean is destructive: it removes the Docker volume and wipes the databases.
  • This is a documented setup procedure, not an independent verification of a successful deployment.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
1 October 2026
Original website title
openfort-xyz/opensigner · Official homepage title · retained in its source language
How we review sourcesSuggest a correction