Design Partner Program

What Anchora is

Anchora is a cryptographic audit-trail API. You hash your data, we anchor the hash on Polygon (or Hyperledger Fabric, or both via Hybrid mode), and anyone re-hashes and verifies cryptographically in 50ms.

Your data stays in your database. We never see it. ~$0.000007 per record at scale.

Shipped, in production, live at anchora.co.in. Playground (no signup) at anchora.co.in/playground.

Who we’re looking for

Companies where one of these is true today (or about to be):

You issue certificates / credentials that employers, regulators, or other institutions need to verify (universities, bootcamps, certification platforms, BGV firms).
You generate AI content that needs MeitY-compliant provenance metadata (LLM platforms, AI video/audio/image products, deepfake-adjacent tools).
You collect sensor / operational data that external stakeholders dispute (drone agritech, supply chain, IoT, healthcare records).
You run a regulated workflow where audit trails matter (fintech KYC, healthcare records, government tenders).

Volume thresholds for a meaningful pilot

Use case	Minimum monthly volume
Credentials / certificates	≥ 100 certs issued/month
AI provenance	≥ 1,000 generated outputs/month
Supply chain / sensor / IoT	≥ 1,000 events/month
Audit trails (fintech / healthcare)	≥ 500 events/month

Below these thresholds, anchoring’s value is theoretical. Above them, the integration earns its keep.

Best fit: founder-led, seed to Series A stage, technical leadership accessible, willing to integrate something new in 1–2 weeks.

Not a fit (yet): post-Series B with procurement gauntlets, companies that have already built their own anchoring layer, anyone needing enterprise SLA + SOC 2 today.

What design partners get

Benefit	Details
6 months free access	No per-record cost during program. You only pay actual blockchain gas (~$0.000007/record), passed through at-cost.
Direct founder support	My phone number. My Slack. Issues fixed within 24 hours, almost always within hours.
Custom roadmap input	Your specific use case shapes the next 6 months of Anchora’s build priorities. Feature requests get real consideration.
Pre-launch access	Hyperledger Fabric mode, Hybrid mode, new SDK features — you get them first, sometimes before public announcement.
White-glove integration	I work with your engineering team directly. Pair-program if needed. Write the integration code with you.
No tickets, no escalation	You ping me, I respond. Founder-direct, every time.
Discounted pricing post-program	When Anchora launches paid tiers, design partners get permanent founding-customer pricing (≥40% off published rates).
Optional co-marketing	Joint blog post, joint LinkedIn launch announcement, podcast slot — all opt-in, all approved by you before publication.

What we ask

In exchange:

Real usage — integrate Anchora into one specific workflow (not a hypothetical). Hit the volume threshold above over the program period.
30-min weekly sync for the first 8 weeks. Drop to bi-weekly after that.
Honest feedback — what’s working, what’s broken, what you wish it did differently. Brutal honesty over polite vagueness.
Permission to use your logo + write a case study after 3 months of successful integration. You approve all drafts before publication.
One warm intro to a peer company that might also be a design partner candidate.
Public testimonial (LinkedIn post, podcast clip, or written quote) when the integration is producing measurable value.

No payment from you. No equity from us. No long-term lock-in — you can exit the program with 30 days notice and we’ll export all your data.

Timeline & structure

Phase	Duration	What happens
Discovery	Week 0–1	60-min scoping call. Identify the one workflow we’ll anchor. Define success criteria.
Integration	Week 1–2	Direct work with your eng team. SDK integration, webhook wiring, test anchors flowing.
Pilot	Week 2–12	Real records flowing through. Weekly syncs. Bug fixes, feature requests, iteration.
Scale	Week 12–26	Volume ramps. We hit your real-world usage patterns. Case study drafting begins.
Graduation	Week 26+	Move to paid plan with founding-customer pricing, OR exit with no obligations.

Examples of “this worked” by month 6

1,000+ records anchored without integration issues or material downtime.
At least one customer-side stakeholder (an employer, auditor, regulator, or end-user) successfully verified an anchored record without contacting your team.
Measurable outcome documented (e.g., “verification time down from 5 days to 50ms,” “insurance claim dispute resolved in hours instead of weeks,” “RFP response now includes verifiable provenance”).
Case study draft approved by you and ready for publication.

If we don’t hit these in 6 months, the integration probably isn’t earning its keep — and we should talk about why honestly.

What we can / can’t do honestly

What we CAN do today

Multi-chain anchoring (Polygon mainnet + Amoy testnet, Hyperledger Fabric)
SHA-256 hashing + 256-record Merkle batching for cost efficiency
AES-256-GCM encryption for sensitive payloads (keys passed per-request, never stored server-side)
Hash-only mode (your raw data never leaves your DB)
Webhook confirmations + API key management
JavaScript SDK + comprehensive API docs
Certificate generation + PDF verification portal
Cloud-hosted (Vercel / Render / Railway / MongoDB Atlas) with high availability during business hours

What we CAN’T do today

SOC 2 / ISO 27001 certifications (deferred until paid tier launches)
Multi-region production deployment with active-active failover
99.99% SLA contracts
24/7 NOC-style support (single-founder support; very responsive during IST business hours + most evenings; best-effort overnight)
Custom blockchain integration beyond Polygon + Fabric (Solana, Avalanche, etc.) without scope discussion
On-premise deployment (cloud-only for now; Hyperledger Fabric private-network deployment is possible with co-engineering)
HIPAA / PCI-DSS compliance attestation (hash-only mode is structurally compliant in spirit, but not yet third-party certified)

Honest stage signal

1 founder (Vigneshwaran B S, Chennai)
14 months in development
Pre-revenue
Formal company setup is in progress
Polygon Hadron Founders Club application in flight
Bootstrapped — no VC, design partner stage is intentional

FAQ

Why design partners instead of regular customers?

Anchora is good but not battle-hardened by 100 paying customers yet. The next 6 months of feedback from 3–5 deeply engaged design partners makes Anchora better than 2 years of guessing what enterprises want. You get founder attention; we get a product that earns its right to charge later.

What happens after the 6-month program?

Three paths. (1) Continue at founding-customer pricing (≥40% off published rates). (2) Exit cleanly with a data export. (3) Graduate to a deeper partnership / co-marketing role. Your choice.

Can we use Anchora for production-critical workflows during the program?

Yes, with eyes open. The product is production-quality but it’s single-founder-supported. If 99.99% uptime is a deal-breaker today, we should wait until paid tier launches. If you’re OK with “almost always up, fixed within hours when not,” we’re fine.

How is our data handled? Are encryption keys exposed?

Hash-only mode means raw data never leaves your database. For optional encryption (used in /anchor/secure), AES-256-GCM keys are passed per-request and never stored server-side. Anchora’s infrastructure has zero ability to decrypt your data even in a worst-case breach scenario. Smart contract on Polygon stores only Merkle roots — no PII, no business data, no identifiable information.

Where is data physically stored?

Anchora API is deployed in regions you select (default: Mumbai bom1 for Indian customers). MongoDB Atlas + Redis are configured for the same region. Hash-only mode means your data never crosses your own network boundary. On-chain anchors live on Polygon (globally distributed by design).

Who owns the IP / data / integration code?

You own everything in your environment. We never see raw data (hash-only mode). On-chain proofs are public hashes — cryptographically opaque. Integration code written in your codebase belongs to you. If we co-write generalized patterns that could inform Anchora’s public SDK or docs (with your permission), we’ll credit you. Your specific business logic, models, or workflows stay yours.

What about pricing transparency post-program?

Founding customer pricing will be at least 40% below published rates. Published rates haven’t launched yet; you’ll see them before non-design-partners do. We commit to no price-gouging — if you stay, your effective rate stays competitive.

Can I get exclusivity in my vertical?

Honest answer: no. We need 3–5 design partners across different verticals to build something durable. But we won’t share your specific use case, integration details, or business logic with another design partner. Generalized learnings inform the roadmap; your specifics stay yours.

How does payment / contracting work during the program?

Design partner period is free, so no invoicing is required. When Anchora launches paid tiers, we’ll formalise the contracting entity at that point. If you need a lightweight founder-direct MOU during the program (some procurement teams require one), we can sign one now — it transfers cleanly to whatever entity we register later.

What happens if Anchora is acquired or shuts down?

(1) Anchors already on Polygon persist forever — no one can take them away. (2) We commit to 30-day data export notice in writing. (3) Architecture is fully documented in our repos — your team or anyone you hire can run a copy of Anchora if needed. (4) Anchora SDK is open enough that you could swap to another anchoring provider with minimal code changes. You’re never locked in.

How do we know this isn’t going to disappear?

Fair question. Mitigations: (1) Full architecture docs in our repo, (2) Infrastructure-as-code, (3) 30-day data export guarantee in writing, (4) On-chain anchors persist on Polygon regardless of Anchora’s status. Even if Anchora vanished tomorrow, your anchored hashes are forever verifiable on-chain by anyone with the original data.

What’s the liability if something breaks?

At design partner stage, we operate on good-faith founder-to-founder terms. The lightweight MOU caps mutual liability at the value of any fees paid (which is $0 during the program). For high-stakes production workflows, we recommend running Anchora alongside your existing systems initially rather than as a replacement. Once we graduate to paid tier, formal liability terms will be negotiated based on use case.

How to engage

Reply to the email or DM that brought you here Say “interested in exploring design partner role.”
30-min scoping call We identify your one workflow + decide if there’s real fit.
2-page partnership memo I draft, you review, we sign (lightweight, lawyer-optional).
Integration kickoff Week 1 starts.

If you’re not the right person but know someone in your org who is, intros are very welcome.

Contact

Vigneshwaran B S

Founder, Anchora

Email: vigneshwaran.bs@anchora.co.in

Web: anchora.co.in

X: @anchora_labs

LinkedIn: linkedin.com/in/vigneshwaranbs

Based in Chennai, India. Available across IST business hours and most evenings.