Random bytes and numbers
Generate random bytes and bounded numbers for security tokens, game logic, simulations, and other application needs.
Cryptographically secure randomness API
Secure random results with evidence you can review later
Rantropy provides random bytes, bounded numbers, shuffling, sampling, and distribution workflows over REST and gRPC. When evidence is enabled, each request can be connected to a receipt, hash chain, and Merkle proof so an important outcome remains traceable after the event.
Preparing for commercial launch
We are preparing the public AWS Marketplace release and can review technical requirements and pilot plans before launch.
API scope
Randomness functions ready for application workflows
A consistent API exposes common random workflows on top of a security-focused randomness core.
Shuffling and sampling
Randomize list order or select samples under defined conditions without rebuilding the core logic in each application.
REST and gRPC
Choose between familiar web integration and persistent, latency-sensitive server connections.
Evidence and review
Make random outcomes reviewable after the event
Requests, output hashes, usage, and timestamps are connected into material that customers and auditors can inspect.
Per-request evidence
Connect each randomness request and result to an identifiable record that can be retrieved when needed.
Integrity verification
Use hash chaining and Merkle proofs to make missing records and later modifications detectable.
Audit export
Provide evidence formats suitable for external review instead of relying only on an internal service screen.
Assurance boundary
Know what the evidence proves
A useful verification model states both its controls and its limits instead of treating every form of verifiable randomness as the same system.
CSPRNG-backed generation
The generation core is designed for security-sensitive randomness, not reproducible simulation output from a user-supplied seed.
Evidence of recorded activity
Receipts and integrity structures show how the service recorded a request and result. They are not a VRF, public beacon, or commit-reveal protocol.
Application responsibility
Authorization, business rules, jurisdictional approval, and independent certification remain separate controls for the customer to operate.
Validation and operations
Review the generator and the production workflow
Statistical testing supports review of output quality, while production readiness also depends on quotas, key handling, failure behavior, evidence capacity, and export verification.
Statistical test context
PractRand, ENT, Dieharder, NIST STS, and TestU01 results are kept with the tested volume and conditions so the numbers can be interpreted correctly.
Plan-aware controls
API quotas, rate limits, receipt generation, retention, exports, and Merkle proofs are applied according to the active contract and evidence policy.
Independent review path
Evidence exports are intended to be checked outside the service screen with documented identifiers, hashes, proof fields, and integrity rules.
Technical guides
Plan the integration and review controls
Use these guides to choose an interface, understand the evidence model, interpret validation results, and prepare regulated random workflows.
Cryptographically secure random APIRequirements, integration choices, and the boundary of receipt-based verification.Read guideRandomness receipts and Merkle proofsHow receipts, hash chains, batches, retention, and independent verification fit together.Read guideREST vs gRPC for randomnessChoose the transport based on connection behavior, latency, operations, and client support.Read guideRandom number generator validationRead statistical test results without confusing a clean report with a security proof.Read guideGaming and lottery randomness auditTechnical evidence and operating controls for draws, games, and licensing preparation.Read guide
Review your randomness API requirements with us
Share your expected request volume, latency target, receipt policy, and preferred AWS Marketplace contract path, and we will help define the rollout scope.