# Advink

*/Startups/Advink*

## Startup Overview

This platform embeds cryptographically secure signing directly into native software workflows. Instead of forcing users to navigate away to a third-party portal to execute agreements, it provides the API infrastructure to keep the entire document lifecycle inside the host application.

Traditional electronic signature tools like DocuSign, HelloSign, and Adobe Acrobat Sign operate as standalone destinations that disrupt user journeys and fracture the brand experience. Software builders and enterprise teams rely on these rigid, seat-based subscriptions that scale poorly for high-volume, variable agreement flows.

By operating as an entirely white-labeled service, the infrastructure remains invisible to the end user and maintains brand continuity from document generation to final execution. A per-completed-transaction pricing model replaces seat licenses, aligning costs directly with successful business outcomes.

## Startup Founding Hypothesis

**Approach**: that embeds cryptographically secure signing into native workflows
**Competitors**:
- [DocuSign](/Competitors/DocuSign)
- [HelloSign](/Competitors/HelloSign)
- [Adobe Acrobat Sign](/Competitors/Adobe_Acrobat_Sign)
**Differentiator2x2**: entirely white-labeled for embedding and priced per completed transaction

## Startup Solution Coordinate

**Solution**: [Advink Signature Engine](/Software/Advink_Signature_Engine)

## Startup Position2x2

```mermaid
quadrantChart
title Market Position: e-Signature Workflows
x-axis Standalone Portal --> Fully White-Labeled Embedding
y-axis Fixed Subscription --> Per-Transaction Pricing
quadrant-1 Utility API
quadrant-2 Niche Utilities
quadrant-3 Traditional SaaS
quadrant-4 Embedded SaaS Tiers
DocuSign: [0.15, 0.15]
Adobe Acrobat Sign: [0.25, 0.20]
HelloSign: [0.75, 0.35]
Advink: [0.90, 0.85]
```

## Startup Brand

**Voice**: Direct and developer-focused, prioritizing integration facts and cryptographic precision.
**Tagline**: Embed cryptographically secure signing natively into your own platform.
**Icon Concept**: nib
**Palette Intent**: institutional-cool
**Visual Identity**: Deep indigo and crisp white palettes pair with strict monospaced typography to emphasize cryptographic precision and seamless developer integration.
**Archetype Reference**: the-sage

## Startup Customer Journey

```mermaid
flowchart LR; A[Developer Search Engine] --> B[API Documentation Portal]; B --> C[Self-Serve Sandbox]; C --> D[Cryptographic Signature Proof]; D --> E[Production SaaS Application]; E --> F[High-Volume API Infrastructure]; F --> G[Agent Tool Registry];
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- A 30-day staging environment pilot targeting the successful generation of 5,000 natively embedded, ESIGN-compliant test contracts without a single external redirect.
- A 60-day parallel deployment within a live HR onboarding flow aiming to prove zero client-side data retention and 100% cryptographic verification under standard application load.
**Target Metrics**:
- Target: 0% user drop-off attributed to external e-signature domain redirects.
- Aim: 100% ESIGN compliance pass rate on mathematically verifiable native audit trails.
- Target: <500ms cryptographic proof generation latency per completed transaction.
- Aim: 40% reduction in per-signature platform costs by paying strictly for completed envelopes rather than abandoned drafts.
**Target Case Studies**:
- A mid-market fintech lending platform that integrates the white-label API to eliminate third-party signature redirects, aiming to increase loan origination completion rates.
- An enterprise HR software vendor that embeds the sandboxed components to keep new hires entirely within their native dashboard during document onboarding.
- A property management SaaS provider that utilizes the cryptographic proof generation to secure multi-party lease agreements natively without relying on legacy e-signature brands.
**Testimonial Targets**:
- VP of Product at a fintech platform validating that the white-label API enabled a completely seamless checkout flow without exposing users to an external vendor's brand.
- CTO of an HR SaaS provider expressing confidence in the zero-retention sandboxed components that simplified their internal security and compliance reviews.
- Director of Engineering at a PropTech startup praising the metered pricing model that only bills for completed, cryptographically sealed transactions to keep unit economics predictable.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Enterprise compliance teams reject the cryptographically secure signatures due to a lack of established legal precedent under frameworks like eIDAS or the ESIGN Act. · Mitigation Status: in-progress
- Severity: high · Description: DocuSign or Adobe Acrobat Sign introduce fully white-labeled, usage-based APIs, instantly erasing the pricing and embedding differentiators. · Mitigation Status: unmitigated
- Severity: high · Description: Native workflow integration proves too technically demanding for customer development teams, resulting in stalled deployments and high sales engineering costs. · Mitigation Status: in-progress
- Severity: moderate · Description: Platform users bundle dozens of signature workflows into a single API payload to exploit the per-completed-transaction pricing model. · Mitigation Status: unmitigated

## Startup Competitors

- [DocuSign](/Competitors/DocuSign) — Incumbent
- [HelloSign](/Competitors/HelloSign) — Incumbent
- [Adobe Acrobat Sign](/Competitors/Adobe_Acrobat_Sign) — Incumbent
- [PandaDoc](/Competitors/PandaDoc) — Alternative Provider
- [Manual PDF Signing](/Competitors/Manual_PDF_Signing) — Status Quo

## Startup Story Brand

**Hero**:
- **Need**: to be the architect of a unified user experience, not an integration specialist
- **Want**: to embed secure document signing natively without redirecting users to third-party sites
- **Identity**: the platform developer at a fintech or HR software company
**Plan**:
- Step: Define · Detail: Choose your UI components and set the custom domain routing to match your application's brand.
- Step: Verify · Detail: Test the cryptographic proof generation in an unlimited developer sandbox to ensure audit chain integrity.
- Step: Deploy · Detail: Go live with usage-based pricing that only bills you for successfully sealed and completed envelopes.
**Guide**:
- **Empathy**: Does your loan origination process still drop users into a DocuSign iframe that breaks your mobile UI?
**Problem**:
- **Villain**: redirect-driven signing
- **External**: Users are forced out of your app into a DocuSign or Adobe Acrobat Sign portal, breaking the conversion funnel and requiring manual webhook management for status updates.
- **Internal**: You feel like your product is a fragmented collection of other people's brands instead of a professional, cohesive platform.
- **Philosophical**: Software integrity belongs in the native user experience, not in a third-party redirect.
**Success**: Your users sign leases and loan documents natively within your interface, while you only pay for completed, cryptographically sealed results.
**One Liner**: What if users never had to leave your app to sign a contract? Advink embeds white-labeled, cryptographically secure signing natively into your workflow, keeping your brand front and center while cutting costs.
**Positioning**:
- **So That**: keep users within your native brand experience
- **Unlike**: DocuSign or Adobe Acrobat Sign redirects
- **For Whom**: Platform developers at fintech and HR companies
- **Category**: Embedded white-label signing API
**Call To Action**:
- **Direct**: Launch API sandbox
- **Transitional**: View cryptographic schema
**Failure Stakes**:
- High user drop-off during redirects
- Branding fragmentation
- Inflated fixed licensing costs
**Transformation**:
- **To**: the engineer who builds seamless native transaction engines
- **From**: a developer stitching together disjointed iFrame redirects
**Controlling Idea**: Native embedding should be the standard for secure digital signatures.

## Startup Story Brand V2

**Hero**:
- **Want**: embed contract signing in their own product with no third-party redirect
- **Identity**: the platform engineer at a fintech, HR, or proptech software company
**Plan**:
- Step: Define your fields · Detail: Lay out signature and initial fields on your own documents in the sandbox.
- Step: Send a test envelope · Detail: Run a signer through your embedded flow and inspect the sealed audit trail.
- Step: Ship to production · Detail: Go live under your own domain and pay only when envelopes complete.
**Problem**:
- **Villain**: the signing redirect
- **External**: Loan and lease packets bounce signers into a DocuSign iframe that breaks the mobile UI, while status crawls back through webhook plumbing the team babysits.
- **Internal**: Every signed deal ends on someone else's screen, and the product starts to feel like a patchwork of other companies' brands instead of one platform.
- **Philosophical**: The signature is the moment a deal becomes real, and the platform that carried the entire journey ought to carry that closing moment too.
**Success**: Leases and loan documents get signed inside your own interface, and every completed envelope carries a self-contained cryptographic proof you can verify without calling anyone's API.
**One Liner**: Advink embeds white-label, ESIGN-compliant signing inside your own product, so signers never bounce to a third-party portal and you pay only for envelopes that complete and seal.
**Call To Action**:
- **Direct**: Launch API sandbox
- **Transitional**: Inspect a sample envelope
**Failure Stakes**:
- Signers drop off inside a third-party redirect
- Seat licenses bill whether envelopes complete or not
- The deal's closing moment carries someone else's brand

## Startup Landing Hero Software V2

**Eyebrow**: Embedded white-label signing API
**Subhead**: When a lease or loan packet reaches the signing step, your platform embeds Advink's white-label API and executes ESIGN-compliant signatures without a redirect.
**Headline**: Signing that never leaves your app
**Announcement**:
- **Text**: Every completed envelope seals with a self-contained, verifiable audit trail
- **Badge**: Audit-first signing
**Supporting Proof**: Designed around the ESIGN Act's cryptographic evidence standards

## Startup Landing Solution V2

**Section Heading**: Own the signature without building the cryptography
**Solution Statement**: Advink is an embedded electronic-signature API and SDK. It renders signing inside the host application's own UI and domain, then returns a cryptographically sealed, ESIGN-compliant audit trail for each completed envelope.

## Startup Landing Features V2

**Benefits**:
- Detail: Borrowers and new hires sign without ever seeing a third-party portal. · Benefit: Keep signers inside your product · Feature: white-label signing components rendered under your own domain and styling
- Detail: Verification works with standard tooling even when the Advink API is unreachable. · Benefit: Prove every signature independently · Feature: self-contained cryptographic proof bound to the document hash at signing
- Detail: Envelope status lands in your database the moment a signer acts. · Benefit: Track envelopes in real time · Feature: standard webhooks for sent, viewed, signed, and sealed envelope events
- Detail: Abandoned drafts, declines, and expired sessions never appear on the invoice. · Benefit: Pay only for completed envelopes · Feature: usage metering that bills solely on cryptographically sealed completions
- Detail: Sensitive agreements stay between the signer and the platform hosting them. · Benefit: Protect document contents structurally · Feature: client-side payload encryption with zero document retention on Advink servers
- Detail: Existing document logic replays in the sandbox before any production cutover. · Benefit: Migrate templates without lock-in · Feature: standard PDF form fields and coordinate mapping imported from DocuSign or Adobe
**Section Heading**: Signature infrastructure your product presents as its own

## Startup Landing Pricing V2

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Tiers**:
- Name: Starter · Unit: per sealed envelope · Model: usage · Recommended: false · Audience Tagline: Fintechs shipping their first embedded signing flow
- Name: Growth · Model: flat · Cadence: mo · Recommended: true · Audience Tagline: Platforms sealing hundreds of envelopes each month
- Name: Scale · Model: custom · Recommended: false · Audience Tagline: High-volume lenders and HR suites with custom needs
**Group Hint**: 2
**Section Heading**: What does a sealed envelope cost?

## Startup Landing Faq V2

**Faqs**:
- Answer: Yes. Every sealed envelope carries a self-contained cryptographic proof mathematically linked to the document hash at signing. You can re-verify integrity with standard hashing tools against your own stored copy, without calling the Advink API or depending on the platform being reachable. · Question: Can I verify signatures if Advink goes down?
- Answer: Nothing. Metering triggers only when an envelope completes and is cryptographically sealed. Drafts that stall, signers who decline, and sessions that expire never generate a billable event, which is the point of pricing on completed transactions instead of seats. · Question: What do abandoned envelopes cost us?
- Answer: The components run sandboxed inside your page, and payload encryption happens client-side before anything leaves the browser. Advink retains no document contents after sealing, so a compromise of Advink's servers would expose hashes and events, not your users' agreements. · Question: Is embedding signing components a security risk?
- Answer: Advink uses standard PDF form fields and coordinate mapping, so existing templates carry over without a proprietary conversion step. You replicate your document logic once in the sandbox, verify a test envelope end to end, then point production traffic at your own signing domain. · Question: How hard is migrating from DocuSign templates?
- Answer: No. Your backend requests a signing session for each participant, and the signer completes everything inside your interface. Identity and authentication events are recorded in the audit trail, but there is no Advink login, branding, or account step in the signer's path. · Question: Do our signers need an Advink account?
- Answer: Any standard PDF with form fields: leases, loan packets, offer letters, NDAs, multi-party agreements. You define signature, initial, and date fields with coordinate mapping, and the same envelope can route several documents to several signers in one signing session. · Question: Which documents and formats does it handle?
**Section Heading**: Questions developers ask before embedding

## Startup Landing Final Cta V2

**Eyebrow**: Your first envelope
**Heading**: When the sandbox opens, sign
**Subhead**: Sandbox keys are self-serve; nothing bills until a production envelope completes and seals.
**Reassurance**: Standard PDF form fields mean templates move in and out without lock-in

## Startup Landing Objection

**Objection**: Will a court accept a signature that didn't come through DocuSign?
**Data Handling**:
- **What We Never**: Decrypted document contents; payloads encrypt client-side and nothing persists after an envelope seals
- **What We Touch**: Document hashes, signer identity and authentication events, and envelope status for each session
**Honest Answer**: Enforceability rests on the evidence, not the logo. Advink binds each signature to the document hash at the moment of signing and records how the signer authenticated, producing a self-contained audit trail aligned with ESIGN and UETA that verifies with standard tools, independent of Advink's servers.
**Residual Risk**: No court has weighed an Advink-sealed envelope yet; the format is designed for scrutiny, not yet tested by it.
**Mechanism Detail**: Each sealed envelope embeds a tamper-evident hash chain plus the authentication record, so the proof re-verifies offline without calling the Advink API.

## Startup Landing Surfaces

**Entities**:
- Icon: lucide:mail · Name: Envelope · Description: A set of documents routed for signature and sealed on completion
- Icon: lucide:user-check · Name: Signer · Description: A participant authenticated and bound to the fields they must complete
- Icon: lucide:shield-check · Name: AuditTrail · Description: The tamper-evident event chain proving who signed what, and when
**Headless**: true
**Functions**:
- Signature: POST /envelopes · Description: Creates an envelope from PDFs and returns its routing state
- Signature: POST /envelopes/{id}/sessions · Description: Issues an embedded signing session token for one signer
- Signature: GET /envelopes/{id}/audit · Description: Returns the sealed audit trail with verifiable document hashes
- Signature: POST /webhooks · Description: Registers an endpoint for envelope viewed, signed, and sealed events
**Code Example**:
- **Code**: const advink = new Advink({ apiKey: process.env.ADVINK_KEY });

const envelope = await advink.envelopes.create({
  documents: [{ name: "unit-4b-lease.pdf", pdf: leasePdf }],
  signers: [
    { email: "tenant@example.com", role: "tenant" },
    { email: "owner@acmelease.com", role: "landlord" },
  ],
  branding: { domain: "sign.acmelease.com" },
});

const session = await advink.envelopes.createSession(envelope.id, { signer: "tenant" });
renderSigningView(session.embedUrl); // signing stays inside your UI
- **Language**: typescript
**Surface List**:
- api
- sdk
- webhook
**Entities Heading**: The signing data model

## Startup Landing Software Workflows

**Workflows**:
- Label: Envelopes · Title: Create and route an envelope · Description: Build an envelope from your PDFs and route it to every signer.
- Label: Sessions · Title: Embed signing in your UI · Description: Issue a session token and render the signing view under your own domain.
- Label: Audit · Title: Verify the sealed trail · Description: Fetch the audit trail and re-verify the document hash yourself.
**Workflows Heading**: Core signing workflows
**Workflows Description**: Create an envelope, embed the session, and verify the sealed trail with three calls.

## Startup Landing Software Code Cards

**Cards**:
- Badge: Reactive · Heading: React to envelope events · Description: Webhooks fire on every envelope transition so downstream records update themselves.
- Badge: Verifiable · Heading: Offline proof verification · Description: Sealed envelopes re-verify against the document hash with no dependency on Advink uptime.
**Code Cards Heading**: Beyond sending envelopes
**Code Cards Description**: Envelope events stream into your systems, and proofs verify without a vendor round trip.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: What if users never had to leave your app to sign a contract? Advink embeds white-labeled, cryptographically secure signing natively into your workflow, keeping your brand front and center while cutting costs.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 4f4fb83f116daff4

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Embedded white-label signing API for Platform developers at fintech and HR companies. Unlike DocuSign or Adobe Acrobat Sign redirects — keep users within your native brand experience.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 8d09f3033fc500ea

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Users are forced out of your app into a DocuSign or Adobe Acrobat Sign portal, breaking the conversion funnel and requiring manual webhook management for status updates.
Solution: What if users never had to leave your app to sign a contract? Advink embeds white-labeled, cryptographically secure signing natively into your workflow, keeping your brand front and center while cutting costs.
Customer: Platform developers at fintech and HR companies
Unlike: DocuSign or Adobe Acrobat Sign redirects
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 3ec15f8a724ac2a9

## Startup Token M E D D P I C C

**Pain**: Users are forced out of your app into a DocuSign or Adobe Acrobat Sign portal, breaking the conversion funnel and requiring manual webhook management for status updates.
**Metrics**: Target: Your users sign leases and loan documents natively within your interface, while you only pay for completed, cryptographically sealed results.
**Rendered**: Pain: Users are forced out of your app into a DocuSign or Adobe Acrobat Sign portal, breaking the conversion funnel and requiring manual webhook management for status updates.
Economic buyer: SaaS Platform
Metrics: Target: Your users sign leases and loan documents natively within your interface, while you only pay for completed, cryptographically sealed results.
Competition: DocuSign or Adobe Acrobat Sign redirects
**Mechanism**: spine-derived-v1
**Competition**: DocuSign or Adobe Acrobat Sign redirects
**Economic Buyer**: SaaS Platform
**Vocab Fingerprint**: e356a2d2b3d6b64f

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Embedded white-label signing API for Platform developers at fintech and HR companies

Platform developers at fintech and HR companies — Users are forced out of your app into a DocuSign or Adobe Acrobat Sign portal, breaking the conversion funnel and requiring manual webhook management for status updates. What if users never had to leave your app to sign a contract? Advink embeds white-labeled, cryptographically secure signing natively into your workflow, keeping your brand front and center while cutting costs.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 3020e2301de9c2b8

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Embedded white-label signing API. What if users never had to leave your app to sign a contract? Advink embeds white-labeled, cryptographically secure signing natively into your workflow, keeping your brand front and center while cutting costs. Serves Platform developers at fintech and HR companies.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 26d345ea7ab1bc29

## Neighborhood

### Candidate solutions

- [Optimize Film Roll Yield](/Problems/Optimize_Film_Roll_Yield) — candidate solution for · Problems

### Composed of

- [Roll Allocation Service](/Services/Roll_Allocation_Service) — composes · Services
- [Geometric Packing Engine](/Agents/Geometric_Packing_Engine) — composes · Agents
- [Template Allocation Agent](/Agents/Template_Allocation_Agent) — composes · Agents
- [Plotter Instruction API](/Agents/Plotter_Instruction_API) — composes · Agents
- [Vector Tessellation Worker](/Agents/Vector_Tessellation_Worker) — composes · Agents
- [Pattern Nesting Service](/Services/Pattern_Nesting_Service) — composes · Services
- [Plotter Command SDK](/Agents/Plotter_Command_SDK) — composes · Agents
- [Pattern Tessellation Agent](/Agents/Pattern_Tessellation_Agent) — composes · Agents
- [Queue Aggregation Agent](/Agents/Queue_Aggregation_Agent) — composes · Agents
- [Irregular Polygon Engine](/Agents/Irregular_Polygon_Engine) — composes · Agents

### What it offers

- [Prism Nest](/Software/Prism_Nest) — offers · Software
- [Advink Signature Engine](/Software/Advink_Signature_Engine) — offers · Software
- [Advink Pattern Engine](/Software/Advink_Pattern_Engine) — offers · Software

### Competitors

- [PandaDoc](/Competitors/PandaDoc) — competes with · Competitors
- [Manual PDF Signing](/Competitors/Manual_PDF_Signing) — competes with · Competitors
- [Adobe Acrobat Sign](/Competitors/Adobe_Acrobat_Sign) — competes with · Competitors
- [HelloSign](/Competitors/HelloSign) — competes with · Competitors
- [DocuSign](/Competitors/DocuSign) — competes with · Competitors
- [CorelDRAW](/Competitors/CorelDRAW) — competes with · Competitors
- [XPEL Design Access Program](/Competitors/XPEL_Design_Access_Program) — competes with · Competitors
- [SunTek TruCut](/Competitors/SunTek_TruCut) — competes with · Competitors
- [3M Pattern and Solutions](/Competitors/3M_Pattern_and_Solutions) — competes with · Competitors
- [manual pattern rotation](/Competitors/manual_pattern_rotation) — competes with · Competitors
- [manual drag-and-drop](/Competitors/manual_drag-and-drop) — competes with · Competitors
- [manual single-vehicle placement](/Competitors/manual_single-vehicle_placement) — competes with · Competitors
- [Manual Template Rotation](/Competitors/Manual_Template_Rotation) — competes with · Competitors
- [Legacy CorelDRAW Plotting](/Competitors/Legacy_CorelDRAW_Plotting) — competes with · Competitors
- [manual single-job nesting](/Competitors/manual_single-job_nesting) — competes with · Competitors
- [Single-Job Manual Nesting](/Competitors/Single-Job_Manual_Nesting) — competes with · Competitors
- [XPEL DAP](/Competitors/XPEL_DAP) — competes with · Competitors
- [Manual Spatial Manipulation](/Competitors/Manual_Spatial_Manipulation) — competes with · Competitors
- [Manual drag-and-drop rotation](/Competitors/Manual_drag-and-drop_rotation) — competes with · Competitors
- [3M Pattern Solutions](/Competitors/3M_Pattern_Solutions) — competes with · Competitors
- [Manual vector templates](/Competitors/Manual_vector_templates) — competes with · Competitors
- [Manual CorelDRAW Adjustments](/Competitors/Manual_CorelDRAW_Adjustments) — competes with · Competitors
- [XPEL Design Access](/Competitors/XPEL_Design_Access) — competes with · Competitors
- [manual drag-and-drop nesting](/Competitors/manual_drag-and-drop_nesting) — competes with · Competitors

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Who it serves

- [Aftermarket Protective Film and Tint Shop](/CompanyTypes/Aftermarket_Protective_Film_and_Tint_Shop) — serves · CompanyTypes

### Similar Startups

- [Primepen](/Startups/Primepen) — similar · Startups
- [Leapsign](/Startups/Leapsign) — similar · Startups
- [Validationsign](/Startups/Validationsign) — similar · Startups
- [Eonsign](/Startups/Eonsign) — similar · Startups
- [Rigorouspalace](/Startups/Rigorouspalace) — similar · Startups
- [Goodsoblem](/Startups/Goodsoblem) — similar · Startups
- [Baygarden](/Startups/Baygarden) — similar · Startups
- [Certifyforge](/Startups/Certifyforge) — similar · Startups
- [Megastamp](/Startups/Megastamp) — similar · Startups
- [Addendumform](/Startups/Addendumform) — similar · Startups
- [Conveyancevault](/Startups/Conveyancevault) — similar · Startups
- [Auroravessel](/Startups/Auroravessel) — similar · Startups
- [Deal](/Startups/Deal) — similar · Startups
- [Chainkey](/Startups/Chainkey) — similar · Startups
- [Vellumhaven](/Startups/Vellumhaven) — similar · Startups
- [Guildseal](/Startups/Guildseal) — similar · Startups
- [Daybreakharbor](/Startups/Daybreakharbor) — similar · Startups
- [Attestationfile](/Startups/Attestationfile) — similar · Startups
- [Acegistry](/Startups/Acegistry) — similar · Startups
- [Pocogn](/Startups/Pocogn) — similar · Startups