Rakkar Digital

• Requires extensive public proof, abundant peer reviews, or deep global references
• Requires clearly published pricing and fully self-serve onboarding
• Requires specific compliance frameworks not publicly documented (e.g., HIPAA, PCI) or strict EU data residency assurances

• API requires IP allowlisting before use, which adds an operational step during integration.
• Pricing detail is not fully visible on public pages and appears to require direct engagement with sales.

No clear public roadmap with dated commitments was found in accessible sources.

No public performance or scale benchmarks were identified.

• SOC and ISO claims exist, but detailed audit artifacts and full SOC reports are not publicly accessible in all cases.
• Data residency, encryption specifics, key management architecture details, and penetration test summaries are not readily available in public materials.

• A public social post by the CEO indicates Rakkar "temporary paused our business" and references a "last operating day." Prospective customers should verify the company's operational status as of March 11, 2026 and request contractual assurances and continuity plans.

End-user discussion threads about using Rakkar were not readily located in accessible Reddit or Hacker News results. Public posts are primarily funding/press reposts and partnership announcements.

• Vanta customer story: Rakkar states it used Vanta and shortened a SOC 2 timeline; this is a partner-published case study and should be treated as a vendor/partner-provided account rather than an independent audit.

Based on partnerships and press coverage, Rakkar emphasizes:

• Regulated custody in key APAC jurisdictions.
• Integration with custody infrastructure providers such as Fireblocks.
• Support for staking and tokenized RWA programs via partners.

• Claim: Rakkar used Vanta to substantially shorten a SOC 2 compliance timeline.
• Critical evaluation:
  • Indicates the vendor invested in compliance automation and tooling.
  • This is a partner-published narrative and does not replace independent audit artifacts; it does not confirm SOC scope, exceptions, or control effectiveness beyond achieving attestation.

Rakkar's announced partnerships (e.g., tokenized RWA access, staking providers, exchange custody mandates) demonstrate commercial activity and ecosystem engagement, but these items are not equivalent to quantified, independently verified ROI or long-term contract performance details.

Most likely fit:

• Mid-market to enterprise institutions (organizations ranging from tens to several thousand employees) where custody governance, approvals, and compliance reporting matter.
• Organizations with sufficient scale to justify custody fees and security overhead.

• Crypto exchanges and brokerages
• Asset managers / funds
• Fintechs offering tokenized products
• Family offices / treasuries with significant digital-asset exposure

• Decision makers: COO, CFO/Head of Treasury, CISO, Head of Compliance/AML, Head of Digital Assets
• End users: Treasury operations, finance controllers, security operations, compliance operations

• Requires regulated custody in Thailand and/or APAC jurisdictions
• Requires governed workflows (multi-approver, policy engine) and auditable reporting
• Wants to integrate custody via API and maintain tight security controls

• Target users: Institutional and enterprise customers (e.g., exchanges, asset managers, funds) that require regulated custody and governance controls.
• Positioning: The vendor describes itself in marketing materials as "Asia’s leading qualified digital asset custodian"; this is a vendor claim and should be validated against independent indicators such as licensing, audits, and customer references.