Calculation Assumptions

Average Size of an Encrypted Message — Complete Structure of a CryptPeer Message

  • Average length: 100 characters (professional message)
  • Plain text size: ~100 bytes
  • With E2E encryption on user terminal: ~1,500 bytes (1.5 KB)
    • Cryptographic headers
    • Encrypted metadata (timestamp, signature, etc.)
    • Cryptographic padding
    • Encrypted message structure
  • Minimal metadata on relay server: ~50-100 bytes
    • Conversation ID (encrypted): Identifier needed for routing (16-32 bytes)
    • Recipient ID(s) (encrypted): For routing to the right users (16-32 bytes)
    • Server timestamp: Date/time of reception by the server (8 bytes)
    • Minimal routing metadata: Technical information for the relay (10-30 bytes)
  • TBtal per stored message: ~1,700 bytes (1.7 KB)

CryptPeer® Architecture: Blind Relay Server

Encryption is performed on the user terminal. The CryptPeer® relay server has no encryption keys and therefore cannot decrypt messages.

  • E2E encryption on client: Messages are encrypted on the user terminal before tryearsmission
  • Already encrypted data: Data arrives at the server already encrypted
  • Blind relay: The server cannot read the content, only relay encrypted data
  • Minimal metadata: Only metadata necessary for minimal routing is present (conversation ID, recipient ID, server timestamp)
  • Encrypted metadata: Sensitive metadata (client timestamp, signature, message type, etc.) is encrypted in the payload and invisible to the server

Storage impact: Server-side metadata is very limited (~50-100 bytes) because the server cannot process decrypted information. Most of the message size (~1.5 KB) consists of encrypted content (text + encrypted metadata + cryptographic overhead).

Note: The CryptPeer Defense version stores no data: tunneled encryption with direct tryearsfer of encrypted messages and files without storage on the relay server.

Message Volume per User — CryptPeer Storage Consumption per User

  • Messages per day per user: 20-50 messages (professional usage)
  • Average: 35 messages/day/user
  • TBtal size/day/user: 35 × 1.7 KB = ~60 KB/day/user
  • Annual consumption per user: 60 KB/day × 365 days = ~22 MB/year/user (messages only)
  • With files (ratio 1 file/10 messages): ~22 MB/year (messages) + ~1.3 GB/year (files) = ~1.3 GB/year/user (total)

Quick calculation rule: 1 GB storage = ~45 users/year (without purge), or ~225 users/year with automatic 5-year purge. Example: 256 GB = ~11,500 users/year without purge, or ~57,500 users with 5-year purge.

Available Disk Configurations

CryptPeer® can run on different disk sizes. Here are the supported configurations:

  • 128 GB: ~115 GB usable (after OS, logs, system)
  • 256 GB: ~230 GB usable (after OS, logs, system)
  • 500 GB: ~450 GB usable (after OS, logs, system)
  • 1 TB: ~920 GB usable (after OS, logs, system)
  • 2 TB: ~1,850 GB usable (after OS, logs, system)

Note: The calculations below use 256 GB as a reference, but detailed tables for all configurations are available further down.

Calculations by Number of Users — CryptPeer® Server Sizing

CryptPeer server sizing: How many users can a CryptPeer server support? What storage capacity for X users? What retention duration for encrypted messages? Discover our detailed calculations to size your CryptPeer® relay server according to the number of users and disk size.

Scenario 1: 10 users (Starter) — CryptPeer storage capacity small team

  • Daily volume: 10 users × 60 KB/day = 600 KB/day = 0.6 MB/day
  • Annual volume: 0.6 MB/day × 365 days = 219 MB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~1 075 years
    • With safety margin (80%) : ~860 years
    • With files and metadata : ~500-700 years

Conclusion: For 10 users, capacity is largely sufficient even without automatic purge. Ideal for small teams, startups, local offices. Optimal CryptPeer server sizing: 128 GB minimum, 256 GB recommended for safety margin.

Scenario 2: 50 users (Professional) — CryptPeer sizing SMEs

  • Daily volume: 50 users × 60 KB/day = 3 000 KB/day = 3 MB/day
  • Annual volume: 3 MB/day × 365 days = 1 095 MB/year = ~1.1 GB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~215 years
    • With safety margin (80%) : ~172 years
    • With files and metadata : ~100-150 years

Conclusion: For 50 users, capacity allows several decades of retention. Ideal configuration for SMEs, departments, medium teams. CryptPeer server sizing recommended: 256 GB for long retention, 500 GB for comfortable margin.

Scenario 3: 100 users — CryptPeer storage capacity extended team

  • Daily volume: 100 users × 60 KB/day = 6 000 KB/day = 6 MB/day
  • Annual volume: 6 MB/day × 365 days = 2 190 MB/year = ~2.2 GB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~107 years
    • With safety margin (80%) : ~86 years
    • With files and metadata : ~50-70 years

Conclusion: For 100 users, capacity allows several decades of retention. Ideal for extended teams, subsidiaries, medium organizations. CryptPeer server sizing recommended: 256 GB minimum, 500 GB for optimal retention.

Scenario 4: 200 users (Business) — CryptPeer sizing large organization

  • Daily volume: 200 users × 60 KB/day = 12 000 KB/day = 12 MB/day
  • Annual volume: 12 MB/day × 365 days = 4 380 MB/year = ~4.4 GB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~54 years
    • With safety margin (80%) : ~43 years
    • With files and metadata : ~25-35 years

Conclusion: For 200 users, capacity allows 25-35 years of retention. Configuration adapted to large organizations, enterprises, institutions. CryptPeer server sizing recommended: 500 GB minimum, 1 TB for long-term retention with files.

Scenario 5: 300 users — CryptPeer storage capacity important organization

  • Daily volume: 300 users × 60 KB/day = 18 000 KB/day = 18 MB/day
  • Annual volume: 18 MB/day × 365 days = 6 570 MB/year = ~6.6 GB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~36 years
    • With safety margin (80%) : ~29 years
    • With files and metadata : ~17-24 years

Conclusion: For 300 users, capacity allows 17-24 years of retention. Ideal for important organizations, groups, multi-site. CryptPeer server sizing recommended: 500 GB minimum, 1 TB highly recommended for comfortable margin.

Scenario 6: 500 users (Enterprise) — CryptPeer sizing large enterprise

  • Daily volume: 500 users × 60 KB/day = 30 000 KB/day = 30 MB/day
  • Annual volume: 30 MB/day × 365 days = 10 950 MB/year = ~11 GB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~21 years
    • With safety margin (80%) : ~17 years
    • With files and metadata : ~10-14 years

Conclusion: For 500 users, capacity allows 10-14 years of retention. Configuration adapted to large enterprises, international groups, major institutions. CryptPeer server sizing recommended: 1 TB minimum, 2 TB for long-term retention and safety margin.

Scenario 7: 750 users — CryptPeer storage capacity very large organization

  • Daily volume: 750 users × 60 KB/day = 45 000 KB/day = 45 MB/day
  • Annual volume: 45 MB/day × 365 days = 16 425 MB/year = ~16.4 GB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~14 years
    • With safety margin (80%) : ~11 years
    • With files and metadata : ~7-9 years

Conclusion: For 750 users, capacity allows 7-9 years of retention. Ideal for very large organizations, multi-national groups, complex institutions. CryptPeer server sizing recommended: 1 TB minimum, 2 TB highly recommended for optimal retention.

Scenario 8: 1000 users (Enterprise Max) — CryptPeer sizing maximum organization

  • Daily volume: 1000 users × 60 KB/day = 60 000 KB/day = 60 MB/day
  • Annual volume: 60 MB/day × 365 days = 21 900 MB/year = ~22 GB/year
  • Storage consumption per user: ~22 MB/year/user
  • Retention duration (256 GB) :
    • Theoretical : ~10 years
    • With safety margin (80%) : ~8 years
    • With files and metadata : ~5-7 years

Conclusion: For 1000 users, capacity allows 5-7 years of retention. Maximum configuration for very large enterprises, international groups, major institutions. CryptPeer server sizing recommended: 2 TB minimum for long-term retention, with automatic purge configured for indefinite operational maintenance.

CryptPeer Sizing Guide — How Many Users per GB?

Quick calculation rule:

  • Average consumption: ~22 MB/year/user (messages + files)
  • Capacity per user: 1 GB = ~45 users/year (without purge)
  • With automatic 5-year purge: 1 GB = ~225 users (operational indefinitely)
  • Example: 256 GB = ~11,500 users/year without purge, or ~57,500 users with 5-year purge

Frequently asked sizing questions:

  • How many users can a CryptPeer 256 GB server support? Up to 200 users comfortably, 500+ with automatic purge.
  • What storage capacity for 100 CryptPeer users? 256 GB minimum, 500 GB recommended for long retention.
  • CryptPeer message retention duration by number of users? See detailed tables below by disk configuration.
  • CryptPeer server sizing for enterprise: 1 TB for 200-1000 users, 2 TB for 1000+ users.

File Impact

File assumptions

  • Average files: Document (500 KB - 2 MB), Image (200 KB - 1 MB), Video (5-50 MB)
  • Ratio: 1 file for 10 messages (realistic ratio)
  • Average file size: 1 MB
  • File volume/day/user: 3.5 files × 1 MB = 3.5 MB/day/user

Recalculation with files (50 users)

  • Messages: 3 MB/day
  • Files: 50 × 3.5 MB = 175 MB/day
  • Total: 178 MB/day = 65 GB/year
  • Duration with files: 235,520 MB ÷ 65,000 MB/year = ~3.6 years
  • With automatic file purge: Much longer

Automatic Management Features

Automatic Message Purge (1-10 years)

  • Operation: Admin defines retention period: 1 to 10 years
  • On exceedance: Automatic deletion of oldest messages
  • Advantage: Guaranteed operational maintenance

Example 50 users: Without purge: ~3.6 years (with files) → With 5-year purge: Operational indefinitely

Automatic File Purge (80% threshold)

  • Threshold: 80% of capacity used
  • Priority: Already downloaded files
  • Mode: Automatic or manual
  • Advantage: Operational maintenance even with large files

Example: 256 GB × 80% = 205 GB threshold → On exceedance: Purge downloaded files → Server remains operational

Summary Tables by Configuration

Configuration 128 GB (~115 GB usable)

Users TBtal/year Duration without purge Duration with 5-year purge
10 13 GB ~9 years ∞ (operational)
50 65 GB ~1.8 years ∞ (operational)
200 260 GB ❌ Exceeded ∞ (operational)

Configuration 256 GB (~230 GB usable)

Users TBtal/year Duration without purge Duration with 5-year purge
10 13 GB ~18 years ∞ (operational)
50 65 GB ~3.6 years ∞ (operational)
200 260 GB ~0.9 an ∞ (operational)
500 650 GB ❌ Exceeded ∞ (operational)

Configuration 500 GB (~450 GB usable)

Users TBtal/year Duration without purge Duration with 5-year purge
10 13 GB ~35 years ∞ (operational)
50 65 GB ~7 years ∞ (operational)
200 260 GB ~1.7 years ∞ (operational)
500 650 GB ~0.7 an ∞ (operational)

Configuration 1 TB (~920 GB usable)

Users TBtal/year Duration without purge Duration with 5-year purge
10 13 GB ~71 years ∞ (operational)
50 65 GB ~14 years ∞ (operational)
200 260 GB ~3.5 years ∞ (operational)
500 650 GB ~1.4 years ∞ (operational)
1000 1 300 GB ❌ Exceeded ∞ (operational)

Configuration 2 TB (~1 850 GB usable)

Users TBtal/year Duration without purge Duration with 5-year purge
10 13 GB ~142 years ∞ (operational)
50 65 GB ~28 years ∞ (operational)
200 260 GB ~7 years ∞ (operational)
500 650 GB ~2.8 years ∞ (operational)
1000 1 300 GB ~1.4 years ∞ (operational)
2000 2 600 GB ❌ Exceeded ∞ (operational)

Conclusion: With automatic purge, the server remains operational indefinitely even with many users.

Recommendations by Configuration

128 GB

  • Ideal for : 10-20 users
  • Retention period: 3-5 years
  • File purge: Automatic at 80%
  • Result: Operational indefinitely

256 GB

  • Ideal for : 10-200 users
  • Retention period: 3-10 years
  • File purge: Automatic at 80%
  • Result: Operational indefinitely

500 GB

  • Ideal for : 50-500 users
  • Retention period: 3-7 years
  • File purge: Automatic at 80%
  • Result: Operational indefinitely

1 TB

  • Ideal for : 200-1000 users
  • Retention period: 3-14 years
  • File purge: Automatic at 80%
  • Result: Operational indefinitely

2 TB

  • Ideal for : 500-2000 users
  • Retention period: 3-28 years
  • File purge: Automatic at 80%
  • Result: Operational indefinitely

Important note: With automatic purge configured, all configurations remain operational indefinitely, regardless of disk size. Automatic purge guarantees operational maintenance by intelligently deleting the oldest data.

For more information: See the Automatic Storage Management section in our features.