# Basiscity

*/Startups/Basiscity*

## Startup Overview

This digital infrastructure ingests disparate hardware telemetry and maps it directly into an active coordinate system. The system normalizes live feeds from distributed sensors into a single, unified spatial graph. External applications query physical spaces logically through this graph rather than writing custom parsers for every new hardware vendor.

Hardware operators and infrastructure developers deal with a fragmented ecosystem of proprietary protocols and siloed dashboards. Instead of forcing teams to build brittle point-to-point integrations, the engine automatically binds incoming telemetry to physical locations and topological relationships. Developers use the spatial graph to trigger automated responses based on proximity, density, or sequential events across disparate sensor networks.

Legacy platforms like Esri ArcGIS and Cisco Kinetic demand massive upfront licensing and proprietary lock-in, while in-house integrations require endless maintenance. In contrast, this system provides an open, developer-extensible core where teams write custom spatial logic using standard tooling. The commercial model abandons user-seat licensing, pricing the service strictly on telemetry throughput to match actual device deployment scale.

## Startup Founding Hypothesis

**Approach**: that normalizes real-time IoT feeds into a spatial graph
**Competitors**:
- [Esri ArcGIS](/Competitors/Esri_ArcGIS)
- [Cisco Kinetic](/Competitors/Cisco_Kinetic)
- [in-house custom integrations](/Competitors/in-house_custom_integrations)
**Differentiator2x2**: developer-extensible and priced purely on telemetry throughput

## Startup Solution Coordinate

**Solution**: [Spatial Graph Engine](/Software/Spatial_Graph_Engine)

## Startup Position2x2

```mermaid
quadrantChart
title Spatial Graph & IoT Telemetry Market
x-axis Closed Ecosystem --> Developer-Extensible
y-axis Seat & License Pricing --> Telemetry Throughput Pricing
quadrant-1 Extensible & Scalable Cost
quadrant-2 Turnkey & Scalable Cost
quadrant-3 Turnkey & Fixed Cost
quadrant-4 Extensible & Fixed Cost
Esri ArcGIS: [0.15, 0.15]
Cisco Kinetic: [0.25, 0.25]
in-house custom integrations: [0.85, 0.15]
Basiscity: [0.90, 0.85]
```

## Startup Offer

**Proof**:
- Targeting sub-second spatial querying for logistics teams tracking 10,000+ active field assets.
- Aiming to eliminate custom integration maintenance for municipal smart city telemetry networks.
- Designed to safely buffer and normalize bursts of up to 500,000 events per second during device reconnections.
**Tiers**:
- Name: Prototyping Node · Price: ~$0.05–$0.10 per million telemetry events · Inclusions: Shared processing capacity for up to 50 million events per month, standard spatial graph indexing, and 7-day data retention designed for development environments.
- Name: Production Grid · Price: ~$0.02–$0.04 per million telemetry events · Inclusions: Uncapped event throughput, sub-second spatial normalization, and full access to the developer-extensible WebAssembly parsing layer.
- Name: Dedicated Fabric · Price: enterprise commit: ~$2,500–$5,000/mo + ~$0.01 per million events · Inclusions: Isolated tenant processing clusters, designed to integrate directly with private cloud VPCs, and custom data retention policies.
**Guarantee**: Promises sub-200ms normalization latency from IoT telemetry ingestion to spatial graph query availability, or the affected month's throughput charges are fully credited to your account.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: Our IoT sensors use proprietary, undocumented binary payloads. Rebuttal: Basiscity features a developer-extensible parsing layer that accepts custom WebAssembly decoders to interpret any payload structure.
- Objection: We cannot risk unpredictable API bills if a sensor malfunctions and spams data. Rebuttal: The platform includes configurable throughput rate-limiting and automatic anomaly blackholing at the ingest edge to cap your spend.
- Objection: We already pay for Esri ArcGIS and do not want another mapping tool. Rebuttal: Basiscity is a high-throughput data pipeline, not a map UI; it is designed to feed clean, real-time spatial state directly into your existing ArcGIS environment.
- Objection: Replacing our custom Kafka pipelines is too risky for production operations. Rebuttal: You can shadow-route a small subset of your device telemetry to validate spatial graph accuracy before deprecating any internal systems.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Developer-centric and terse, leading with architectural facts and query capabilities.
**Tagline**: Map real-time IoT feeds onto a queryable spatial graph.
**Icon Concept**: sensor
**Palette Intent**: electric-signal
**Visual Identity**: The visual identity pairs deep charcoal backgrounds with neon cyan accents, using subtle topographic grid patterns to emphasize real-time spatial telemetry.
**Archetype Reference**: the-creator

## Startup Buyer Chain

**Chain**: Basiscity → IoT Developer → Facility Operations Team
**Gtm Motion**: Acquires developers through self-serve API sandboxes and technical documentation for spatial mapping. Expands revenue purely on usage as engineering teams connect more sensors and increase total telemetry throughput.
**Agent Channel**: Designed to publish a machine-readable OpenAPI schema and target listing in the Model Context Protocol (MCP) ecosystem, allowing autonomous infrastructure agents to discover and query the spatial graph directly.
**Primary Channel**: Organic search by spatial engineers querying for 'real-time IoT graph API' alongside intended technical distributions through GitHub and the AWS Marketplace.

## Startup Customer Journey

```mermaid
flowchart LR
  A[AWS Marketplace] --> C[API Sandbox]
  B[Model Context Protocol] --> C
  C --> D[WebAssembly Parser]
  D --> E[Spatial Graph Environment]
  E --> F[Facility Operations Team]
  F --> G[Dedicated Fabric Cluster]
  G --> H[GitHub Repository]
```

## Startup Proof Points

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

**Pilot Goals**:
- 30-day shadow-routing pilot: Duplicate a subset of live fleet telemetry to validate spatial graph accuracy and ingestion latency before deprecating legacy pipelines.
- 14-day payload decoding sprint: Implement and test custom WebAssembly decoders to prove Basiscity can interpret the client undocumented proprietary binary payloads at scale.
**Target Metrics**:
- Target: <200ms latency from raw telemetry ingestion to spatial graph query availability.
- Target: 500,000 events per second peak ingestion buffering capacity during fleet reconnections.
- Aim: 100 percent reduction in custom payload integration maintenance via the WebAssembly parsing layer.
**Target Case Studies**:
- Global logistics enterprise tracking 10,000+ field assets: Validate the ability to ingest unstructured telemetry and normalize it into queryable spatial data with sub-second latency.
- Municipal smart city consortium: Demonstrate the elimination of custom Kafka pipeline maintenance by routing raw sensor data through Basiscity directly into their existing ArcGIS environment.
- Industrial automation provider: Prove the platform can safely buffer and decode proprietary binary payloads during network reconnection bursts using custom WebAssembly decoders.
**Testimonial Targets**:
- VP of Engineering at a logistics firm: Expressing relief that they no longer have to maintain custom Kafka pipelines for high-throughput spatial telemetry.
- Head of IoT Data Operations: Validating that the automatic anomaly blackholing successfully capped their API spend during a sensor malfunction.
- Lead GIS Developer: Confirming that the pipeline feeds clean, real-time spatial state seamlessly into their existing ArcGIS setup without needing a new mapping UI.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Backend cloud compute costs for real-time spatial graph updates scale exponentially, destroying unit economics under a flat throughput pricing model. · Mitigation Status: in-progress
- Severity: high · Description: Normalizing legacy, proprietary industrial IoT protocols proves technically infeasible, restricting the platform to only modern web-connected sensors. · Mitigation Status: unmitigated
- Severity: high · Description: Enterprises reject variable throughput-based billing due to budget unpredictability, choosing to remain with predictable fixed-license competitors. · Mitigation Status: in-progress
- Severity: moderate · Description: Developers refuse to adopt a new spatial query format, opting to build custom Python pipelines directly into PostGIS instead. · Mitigation Status: unmitigated

## Startup Competitors

- [Esri ArcGIS](/Competitors/Esri_ArcGIS) — Incumbent
- [Cisco Kinetic](/Competitors/Cisco_Kinetic) — IoT Platform
- [In-House Custom Integrations](/Competitors/In-House_Custom_Integrations) — Status Quo
- [Azure Digital Twins](/Competitors/Azure_Digital_Twins) — Incumbent
- [AWS IoT Core](/Competitors/AWS_IoT_Core) — Cloud Platform

## Startup Solution Stack

- [Telemetry Spatialization Service](/Services/Telemetry_Spatialization_Service) — Service-as-Software
- [IoT Ingestion Worker](/Agents/IoT_Ingestion_Worker) — Agent
- [Spatial Graph Engine](/Software/Spatial_Graph_Engine) — Software
- [Stream Normalization API](/Software/Stream_Normalization_API) — Software
- [Graph Extension SDK](/Software/Graph_Extension_SDK) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the architect of a reliable data infrastructure, not a pipeline repairman
- **Want**: to normalize high-velocity sensor telemetry into a queryable spatial graph
- **Identity**: the IoT engineer at a logistics or smart-city enterprise
**Plan**:
- Step: Upload decoders · Detail: Deploy custom WebAssembly parsers to interpret your proprietary binary sensor payloads at the ingest edge.
- Step: Check telemetry · Detail: Monitor real-time event throughput while our spatial graph indexes the relationship between your 10,000+ active assets.
- Step: Query state · Detail: Pull clean, normalized spatial data directly into Esri ArcGIS or your private cloud VPC.
**Guide**:
- **Empathy**: When a sensor malfunction triggers a 500,000-event-per-second spike, your downstream ArcGIS dashboards freeze and the integration layer crashes.
**Problem**:
- **Villain**: unstructured telemetry sprawl
- **External**: Converting raw binary IoT payloads into usable ArcGIS layers requires maintaining fragile, custom-coded Kafka pipelines that break during device reconnect bursts.
- **Internal**: You feel like a plumber patching leaks in an endless mess of undocumented sensor protocols.
- **Philosophical**: Every engineer deserves to query their physical assets — not spend their career writing parsers for proprietary hex strings.
**Success**: Real-time asset visibility with sub-second spatial querying and zero pipeline maintenance.
**One Liner**: Every hour, IoT engineers fight broken sensor pipelines. Basiscity normalizes telemetry into a spatial graph so field assets are instantly queryable.
**Positioning**:
- **So That**: normalize millions of telemetry events with sub-200ms latency
- **Unlike**: In-house custom Kafka integrations
- **For Whom**: IoT engineers at logistics enterprises
- **Category**: Real-time spatial data pipeline
**Call To Action**:
- **Direct**: Deploy Production Grid
- **Transitional**: Download Wasm parser schema
**Failure Stakes**:
- System-wide dashboard lag
- High maintenance overhead
- Unpredictable API billing spikes
**Transformation**:
- **To**: building spatial applications instead of maintaining data pipelines
- **From**: a devops lead debugging hex logs in Kafka
**Controlling Idea**: IoT telemetry should be a queryable graph, not a maintenance burden.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every hour, IoT engineers fight broken sensor pipelines. Basiscity normalizes telemetry into a spatial graph so field assets are instantly queryable.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 401b8e639558010a

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Real-time spatial data pipeline for IoT engineers at logistics enterprises. Unlike In-house custom Kafka integrations — normalize millions of telemetry events with sub-200ms latency.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: ca754dba61a6c4f2

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Converting raw binary IoT payloads into usable ArcGIS layers requires maintaining fragile, custom-coded Kafka pipelines that break during device reconnect bursts.
Solution: Every hour, IoT engineers fight broken sensor pipelines. Basiscity normalizes telemetry into a spatial graph so field assets are instantly queryable.
Customer: IoT engineers at logistics enterprises
Unlike: In-house custom Kafka integrations
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 3132fd7d92b97364

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

**Pain**: Converting raw binary IoT payloads into usable ArcGIS layers requires maintaining fragile, custom-coded Kafka pipelines that break during device reconnect bursts.
**Metrics**: Target: Real-time asset visibility with sub-second spatial querying and zero pipeline maintenance.
**Rendered**: Pain: Converting raw binary IoT payloads into usable ArcGIS layers requires maintaining fragile, custom-coded Kafka pipelines that break during device reconnect bursts.
Economic buyer: IoT Developer
Metrics: Target: Real-time asset visibility with sub-second spatial querying and zero pipeline maintenance.
Competition: In-house custom Kafka integrations
**Mechanism**: spine-derived-v1
**Competition**: In-house custom Kafka integrations
**Economic Buyer**: IoT Developer
**Vocab Fingerprint**: 401f9734f8030e36

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Real-time spatial data pipeline for IoT engineers at logistics enterprises

IoT engineers at logistics enterprises — Converting raw binary IoT payloads into usable ArcGIS layers requires maintaining fragile, custom-coded Kafka pipelines that break during device reconnect bursts. Every hour, IoT engineers fight broken sensor pipelines. Basiscity normalizes telemetry into a spatial graph so field assets are instantly queryable.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 49786e857f45215c

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Real-time spatial data pipeline. Every hour, IoT engineers fight broken sensor pipelines. Basiscity normalizes telemetry into a spatial graph so field assets are instantly queryable. Serves IoT engineers at logistics enterprises.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: d0df7ecda874e764

## Neighborhood

### Candidate solutions

- [Grower Packout Settlement Disputes](/Problems/Grower_Packout_Settlement_Disputes) — candidate solution for · Problems

### Composed of

- [Telemetry Spatialization Service](/Services/Telemetry_Spatialization_Service) — composes · Services
- [Graph Extension SDK](/Software/Graph_Extension_SDK) — composes · Software
- [Stream Normalization API](/Software/Stream_Normalization_API) — composes · Software
- [Spatial Graph Engine](/Software/Spatial_Graph_Engine) — composes · Software
- [IoT Ingestion Worker](/Agents/IoT_Ingestion_Worker) — composes · Agents

### Embodies

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

### Competitors

- [Cisco Kinetic](/Competitors/Cisco_Kinetic) — competes with · Competitors
- [AWS IoT Core](/Competitors/AWS_IoT_Core) — competes with · Competitors
- [Azure Digital Twins](/Competitors/Azure_Digital_Twins) — competes with · Competitors
- [In-House Custom Integrations](/Competitors/In-House_Custom_Integrations) — competes with · Competitors
- [Esri ArcGIS](/Competitors/Esri_ArcGIS) — competes with · Competitors

### Similar Startups

- [Spherelevel](/Startups/Spherelevel) — similar · Startups
- [Twinbase](/Startups/Twinbase) — similar · Startups
- [Almelematics](/Startups/Almelematics) — similar · Startups
- [Animoct](/Startups/Animoct) — similar · Startups
- [Fordyn](/Startups/Fordyn) — similar · Startups
- [Digitalcube](/Startups/Digitalcube) — similar · Startups
- [Geopivot](/Startups/Geopivot) — similar · Startups
- [Layerfield](/Startups/Layerfield) — similar · Startups
- [Atlas](/Startups/Atlas) — similar · Startups
- [Blazehicle](/Startups/Blazehicle) — similar · Startups
- [Sphererange](/Startups/Sphererange) — similar · Startups
- [Clearlinemap](/Startups/Clearlinemap) — similar · Startups
- [Pulsebridge](/Startups/Pulsebridge) — similar · Startups
- [Almentry](/Startups/Almentry) — similar · Startups
- [Fleetloft](/Startups/Fleetloft) — similar · Startups
- [Willow](/Startups/Willow) — similar · Startups
- [Keystoneridge](/Startups/Keystoneridge) — similar · Startups
- [Amberfusion](/Startups/Amberfusion) — similar · Startups
- [Arrealer](/Startups/Arrealer) — similar · Startups
- [Floorward](/Startups/Floorward) — similar · Startups