Cowrie Research

para-company-primary-sources-2026-08-10

3 min read

Para company primary-source snapshot

Fetched: 2026-08-10 UTC

1) Official homepage

Source: https://www.getpara.com/

Selected excerpts from the official site:

The Complete Wallet-As-A-Service Platform

Build, customize, and scale with embedded wallets, authentication, and money movement.

Policy Engine and Access Controls

A programmable permissions layer that lets you set rules, enforce compliance, and tailor user experiences.

Additional signals from the homepage:

  • Para is explicitly marketing one company-run bundle rather than a narrow signer primitive: embedded wallets, auth, money movement, and policy controls sit on one landing page
  • The site says Para is trusted by 100s of Devs and 15M+ Users, which should still be treated as a vendor claim but helps show the intended operating scale

2) Docs welcome page

Source: https://docs.getpara.com/

Selected excerpts from the docs:

Para is the most comprehensive wallet and authentication suite for crypto and fintech developers.

Para is an all-in-one developer suite to easily provision and manage embedded wallets directly within applications.

trusted by 100+ teams and their 15M+ users

Additional signals from the docs:

  • The docs make the company boundary visible by routing builders through one hosted developer suite rather than a neutral protocol spec
  • The current docs surface support for EVM, Solana, Cosmos, and Stellar plus web, mobile, server, and API integrations

3) Key-management docs

Source: https://docs.getpara.com/v2/concepts/key-management

Selected excerpts from the docs:

Para uses a 2-of-2 Multi-Party Computation (MPC) system.

The two key shares are:

  1. User Share …
  2. Para Share: stored in Para’s cloud hardware security modules (HSMs).

To sign a transaction, both shares participate in a cryptographic signing ceremony … without ever reconstructing the full private key.

Para uses the DKLS19 MPC algorithm

Additional signals from the docs:

  • Para’s operator role is explicit: the Para share lives in Para-managed HSMs and remains part of the signing and recovery path
  • The docs frame passkeys, secure enclaves, and WebAuthn as part of the production workflow, not only as background implementation detail

4) Permissions docs

Source: https://docs.getpara.com/v2/concepts/permissions

Selected excerpts from the docs:

Control exactly what each application can do with a user’s wallet: scoped, transparent, and enforced server-side

Policies are defined per API key, enforced server-side on every transaction, and presented to users as plain-language consent items.

Default deny: any action not explicitly allowed in the policy is blocked

policies … are immutable once published; changes require a new version.

Additional signals from the docs:

  • This is the cleanest evidence that Para is an operator policy layer, not merely an MPC library
  • Policy versioning, API-key scoping, and server-side evaluation create a durable company-run control surface above the keys themselves

5) Developer portal setup docs

Source: https://docs.getpara.com/v3/general/developer-portal-setup

Selected excerpts from the docs:

Get your API key and configure your Para integration through the developer portal.

Your API key is required to initialize the Para SDK and enables you to manage your application’s settings including supported networks, allowed domains, and email configuration.

every integration starts with a Para project and API key

Additional signals from the docs:

  • The current portal docs make project creation, environment selection, network requirements, allowed origins, and email behavior first-class controls
  • The docs also point to adjacent security, permissions, and payments configuration, reinforcing that Para is a hosted workflow shell around wallets rather than only signer middleware

Notes

  • This pass did not locate a classic Para whitepaper or litepaper from official sources.
  • The strongest current sources for the entity split were the homepage, welcome docs, key-management docs, permissions docs, and developer-portal setup docs.
  • Para is best read as a company-run wallet, auth, policy, and movement control plane whose hosted project / API-key / HSM / permissions workflow matters more than any abstract embedded wallet label.

Graph View