# Granie

*/Startups/Granie*

## Startup Overview

This edge-native authorization engine enforces granular access policies across distributed microservices. It moves permissions logic out of centralized servers and directly to the edge network, allowing developers to define and execute fine-grained access rules exactly where the requests arrive.

Software teams building globally distributed applications face structural latency when relying on central servers to verify user permissions. Every request demands a costly network roundtrip just to check a user's access rights. By executing policy checks directly at the edge, the platform eliminates these authorization chokepoints and maintains low response times regardless of the user's physical location.

While traditional identity platforms like Auth0 and centralized policy engines like Oso force traffic back to core infrastructure, this architecture operates independently at the network periphery. As a schema-agnostic system, it adapts to existing data structures and evaluates authorization rules locally, replacing fragile in-house policy engines with zero-latency edge enforcement.

## Startup Founding Hypothesis

**Approach**: that enforces granular access policies across distributed edge microservices
**Competitors**:
- [Auth0](/Competitors/Auth0)
- [Oso](/Competitors/Oso)
- [In-house Policy Engines](/Competitors/In-house_Policy_Engines)
**Differentiator2x2**: schema-agnostic and edge-native, eliminating the latency of centralized authorization checks

## Startup Solution Coordinate

**Solution**: [Granie Access Fabric](/Software/Granie_Access_Fabric)

## Startup Position2x2

```mermaid
quadrantChart
    x-axis Centralized --> Edge-Native
    y-axis Schema-Bound --> Schema-Agnostic
    Auth0: [0.15, 0.25]
    In-house Policy Engines: [0.30, 0.20]
    Oso: [0.40, 0.75]
    Granie: [0.85, 0.85]
```

## Startup Offer

**Proof**:
- Targeting <10ms P99 latency for complex authorization policy evaluations across global edge nodes.
- Aiming to reduce central database authorization query loads by up to 80% for high-traffic distributed architectures.
- Designed to evaluate thousands of concurrent access requests per second without bottlenecking application performance.
**Tiers**:
- Name: Developer Sandbox · Price: Free · Inclusions: Up to 5 million edge authorization evaluations per month, standard community support, and deployment to shared edge nodes for testing.
- Name: Production Edge · Price: ~$0.15–$0.30 per 1M evaluations · Inclusions: Unlimited policy evaluations, multi-region edge deployment, schema-agnostic JSON payload processing, and a 99.9% uptime SLA.
- Name: Enterprise Backbone · Price: ~$25k–$50k/yr minimum commit · Inclusions: Dedicated edge execution environments, highly complex ABAC/RBAC WASM compilation support, 99.99% SLA, and priority integration assistance.
**Guarantee**: Guarantees sub-10ms authorization evaluation latency at the edge; if average latency exceeds this threshold in any billing period, customers are eligible for a prorated refund of that month's usage.
**Business Function**: ProvideService
**Objection Handlers**:
- Latency concerns: Edge execution sounds great until state syncing adds overhead. -> Granie is designed to replicate compiled policies directly to edge nodes, eliminating round-trips to central databases for standard access checks.
- Data model lock-in: We use a highly customized user schema. -> Granie is schema-agnostic and intended to process custom JSON payloads, meaning you never have to rewrite your application's data model to fit our engine.
- Complexity limits: Edge runtimes usually choke on complex ABAC rules. -> Granie aims to compile complex policies into highly optimized, lightweight WebAssembly binaries that execute efficiently within edge constraints.
- Migration disruption: Ripping out Auth0 or an in-house engine is too risky. -> Granie is designed to sit alongside existing Identity Providers, handling the granular authorization layer at the edge while letting your current systems continue managing user identity.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative technical register defined by absolute precision
**Tagline**: Enforce granular access at the edge with zero latency
**Icon Concept**: turnstile
**Palette Intent**: electric-signal
**Visual Identity**: High-contrast interfaces use neon cyan and deep indigo accents against stark black backgrounds, paired with strict monospaced typography to reflect low-latency developer environments.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: Granie → Platform Engineering → Edge Microservice Developers
**Gtm Motion**: Acquires users through bottom-up developer adoption via a free evaluation tier for individual edge clusters. Expands when platform engineering teams standardize the policy engine across the enterprise, transitioning them to a paid managed control plane for global policy distribution.
**Agent Channel**: Designed to list its SDK and policy schema definitions in autonomous coding agent registries like Cursor and Devin, allowing AI developers to automatically discover and implement the authorization logic during edge service scaffolding.
**Primary Channel**: Technical SEO and GitHub repository visibility targeting backend developers searching for solutions to centralized authorization latency and edge-native RBAC implementations.

## Startup Customer Journey

```mermaid
flowchart LR; A[GitHub Repository] --> B[Coding Agent Registry]; B --> C[SDK Documentation]; C --> D[Developer Sandbox]; D --> E[Edge Cluster]; E --> F[Managed Control Plane]; F --> G[Platform Engineering Team];
```

## Startup Proof Points

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

**Pilot Goals**:
- A 14-day shadow-traffic pilot running Granie alongside an existing authorization engine, aimed at proving sub-10ms P99 latency execution on the standard Production Edge tier.
- A 30-day proof-of-concept integrating Granie's WASM compilation with an enterprise team's custom user schema, targeting zero required data model rewrites to execute their current RBAC rules.
**Target Metrics**:
- Target: <10ms P99 latency for complex authorization policy evaluations across global edge nodes.
- Target: 80% reduction in central database authorization query loads for high-traffic distributed architectures.
- Aim: Zero required application data model rewrites to implement edge-based access checks.
- Aim: 10,000+ concurrent access evaluations per second processed per edge region without central database round-trips.
**Target Case Studies**:
- A high-traffic consumer application (Engineering VP) shifting granular access checks from a central database to the edge, aiming to reduce API response times across international regions by executing compiled policies directly on edge nodes.
- A B2B enterprise SaaS provider (Lead Software Architect) migrating complex Attribute-Based Access Control (ABAC) rules to WebAssembly edge binaries, targeting an 80% reduction in central database load without ripping out their existing identity provider.
- A distributed media platform (Platform Engineering Director) deploying schema-agnostic JSON payloads to shared edge nodes, aiming to securely evaluate thousands of concurrent access requests per second during major live-streaming traffic spikes.
**Testimonial Targets**:
- VP of Engineering validating that Granie successfully intercepts and evaluates custom JSON access checks at the edge without requiring any modification to their existing Auth0 identity stack.
- Chief Architect confirming that highly complex ABAC policies compile smoothly into lightweight WebAssembly binaries without choking edge runtimes.
- Lead Developer highlighting the cost predictability and zero-friction scaling of the usage-metered tier after surpassing the 5 million free monthly evaluation threshold.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: State synchronization delays across distributed edge nodes create temporary unauthorized access windows. · Mitigation Status: unmitigated
- Severity: high · Description: Developer teams reject proprietary schema-agnostic policy definitions in favor of established OPA standards. · Mitigation Status: in-progress
- Severity: high · Description: Policy payload sizes negate latency improvements when distributed to edge microservices over low-bandwidth connections. · Mitigation Status: unmitigated
- Severity: moderate · Description: Complex integration requirements with legacy centralized identity providers stall enterprise proof-of-concept deployments. · Mitigation Status: in-progress

## Startup Competitors

- [Auth0](/Competitors/Auth0) — Centralized IdP
- [Oso](/Competitors/Oso) — Developer AuthZ
- [In-house Policy Engines](/Competitors/In-house_Policy_Engines) — Status Quo
- [Open Policy Agent](/Competitors/Open_Policy_Agent) — Incumbent OSS
- [SpiceDB](/Competitors/SpiceDB) — Centralized Zanzibar AuthZ

## Startup Solution Stack

- [Access Enforcement Service](/Services/Access_Enforcement_Service) — Service-as-Software
- [Policy Sync Worker](/Agents/Policy_Sync_Worker) — Agent
- [Edge Authorization Agent](/Agents/Edge_Authorization_Agent) — Agent
- [Agnostic Policy Engine](/Software/Agnostic_Policy_Engine) — Software
- [Microservice Auth SDK](/Software/Microservice_Auth_SDK) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the architect of a resilient infrastructure instead of a bottleneck for performance
- **Want**: to enforce granular access policies across microservices without adding user-facing latency
- **Identity**: the platform engineer at a distributed edge-computing company
**Plan**:
- Step: Define · Detail: Write your custom access logic using our schema-agnostic JSON format for any user data model.
- Step: Verify · Detail: Simulate policy evaluations in the Developer Sandbox to ensure sub-10ms P99 latency.
- Step: Deploy · Detail: Push compiled policies to global edge nodes to handle thousands of concurrent requests per second.
**Guide**:
- **Empathy**: Does your authorization logic still choke global performance during high-traffic spikes?
**Problem**:
- **Villain**: centralized authorization bottlenecks
- **External**: Auth0 and in-house policy engines force global requests back to central databases, adding hundreds of milliseconds to every API call
- **Internal**: You feel like you are sacrificing application speed just to keep the system secure
- **Philosophical**: Why should security protocols degrade the user experience when localized execution is possible?
**Success**: Granular access is enforced globally with sub-10ms latency, and central database auth loads drop by 80%.
**One Liner**: Every millisecond, platform engineers fight authorization lag. Granie enforces granular access at the edge so security never slows down the application.
**Positioning**:
- **So That**: enforce complex ABAC policies with sub-10ms global latency
- **Unlike**: centralized providers like Auth0
- **For Whom**: platform engineers at distributed companies
- **Category**: Edge-native authorization platform
**Call To Action**:
- **Direct**: Deploy edge policy
- **Transitional**: Explore WASM benchmarks
**Failure Stakes**:
- High latency causing user churn
- Database meltdowns from auth query loads
- Security gaps in distributed services
**Transformation**:
- **To**: architecting zero-latency edge security instead of managing database round-trips
- **From**: a developer managing sluggish in-house policy engines
**Controlling Idea**: Authorization should live at the edge to preserve application performance.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every millisecond, platform engineers fight authorization lag. Granie enforces granular access at the edge so security never slows down the application.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 13cbc53c91d60ecb

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Edge-native authorization platform for platform engineers at distributed companies. Unlike centralized providers like Auth0 — enforce complex ABAC policies with sub-10ms global latency.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 9b937b5d10e1fb6f

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Auth0 and in-house policy engines force global requests back to central databases, adding hundreds of milliseconds to every API call
Solution: Every millisecond, platform engineers fight authorization lag. Granie enforces granular access at the edge so security never slows down the application.
Customer: platform engineers at distributed companies
Unlike: centralized providers like Auth0
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 065c5d93c068ed52

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

**Pain**: Auth0 and in-house policy engines force global requests back to central databases, adding hundreds of milliseconds to every API call
**Metrics**: Target: Granular access is enforced globally with sub-10ms latency, and central database auth loads drop by 80%.
**Rendered**: Pain: Auth0 and in-house policy engines force global requests back to central databases, adding hundreds of milliseconds to every API call
Economic buyer: Platform Engineering
Metrics: Target: Granular access is enforced globally with sub-10ms latency, and central database auth loads drop by 80%.
Competition: centralized providers like Auth0
**Mechanism**: spine-derived-v1
**Competition**: centralized providers like Auth0
**Economic Buyer**: Platform Engineering
**Vocab Fingerprint**: 451185a4c47ff737

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Edge-native authorization platform for platform engineers at distributed companies

platform engineers at distributed companies — Auth0 and in-house policy engines force global requests back to central databases, adding hundreds of milliseconds to every API call Every millisecond, platform engineers fight authorization lag. Granie enforces granular access at the edge so security never slows down the application.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 0310c3e0d80a6c88

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Edge-native authorization platform. Every millisecond, platform engineers fight authorization lag. Granie enforces granular access at the edge so security never slows down the application. Serves platform engineers at distributed companies.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: b4917d8f6e7dc588

## Neighborhood

### Candidate solutions

- [Unpredictable Die Tooling Wear](/Problems/Unpredictable_Die_Tooling_Wear) — candidate solution for · Problems

### What it offers

- [Granie Access Fabric](/Software/Granie_Access_Fabric) — offers · Software

### Composed of

- [Access Enforcement Service](/Services/Access_Enforcement_Service) — composes · Services
- [Microservice Auth SDK](/Software/Microservice_Auth_SDK) — composes · Software
- [Policy Sync Worker](/Agents/Policy_Sync_Worker) — composes · Agents
- [Edge Authorization Agent](/Agents/Edge_Authorization_Agent) — composes · Agents
- [Agnostic Policy Engine](/Software/Agnostic_Policy_Engine) — composes · Software

### Embodies

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

### Competitors

- [Open Policy Agent](/Competitors/Open_Policy_Agent) — competes with · Competitors
- [SpiceDB](/Competitors/SpiceDB) — competes with · Competitors
- [Auth0](/Competitors/Auth0) — competes with · Competitors
- [Oso](/Competitors/Oso) — competes with · Competitors
- [In-house Policy Engines](/Competitors/In-house_Policy_Engines) — competes with · Competitors

### Similar Startups

- [Authairie](/Startups/Authairie) — similar · Startups
- [Granooling](/Startups/Granooling) — similar · Startups
- [Domor](/Startups/Domor) — similar · Startups
- [Luminousgate](/Startups/Luminousgate) — similar · Startups
- [Halolayer](/Startups/Halolayer) — similar · Startups
- [Coregate](/Startups/Coregate) — similar · Startups
- [Gatesphere](/Startups/Gatesphere) — similar · Startups
- [Octity](/Startups/Octity) — similar · Startups
- [Capabilityhaven](/Startups/Capabilityhaven) — similar · Startups
- [Staborus](/Startups/Staborus) — similar · Startups
- [Boundeam](/Startups/Boundeam) — similar · Startups
- [Datapalace](/Startups/Datapalace) — similar · Startups
- [Hegen](/Startups/Hegen) — similar · Startups
- [Florix](/Startups/Florix) — similar · Startups
- [Latticeforge](/Startups/Latticeforge) — similar · Startups
- [Problematic](/Startups/Problematic) — similar · Startups
- [Weavermanor](/Startups/Weavermanor) — similar · Startups
- [Anthembasis](/Startups/Anthembasis) — similar · Startups
- [Vipot](/Startups/Vipot) — similar · Startups
- [Edgelock](/Startups/Edgelock) — similar · Startups