# Portyn

*/Startups/Portyn*

## Startup Overview

This digital infrastructure aggregates fragmented terminal yard events into standardized timelines. It ingests raw, unformatted data from disparate port systems and normalizes it into a single, cohesive event feed for container tracking.

Freight forwarders and drayage dispatchers face constant blind spots when tracking container movements across different marine terminals. Rather than relying on delayed legacy EDI connections or manual terminal portal scraping, logistics teams use this feed to access an immediate, unified view of yard activity and coordinate container pickups without accruing demurrage fees.

Unlike generic supply chain visibility networks like Project44 that offer broad but shallow tracking, this solution operates through deep, programmatic integrations directly at the terminal level. It aligns cost directly with tracking outcomes by pricing purely per successful container lifecycle.

## Startup Founding Hypothesis

**Approach**: that aggregates fragmented terminal yard events into standardized timelines
**Competitors**:
- [Legacy EDI connections](/Competitors/Legacy_EDI_connections)
- [Manual terminal portal scraping](/Competitors/Manual_terminal_portal_scraping)
- [Project44](/Competitors/Project44)
**Differentiator2x2**: programmatically integrated and priced purely per successful container lifecycle

## Startup Solution Coordinate

**Solution**: [Terminal Event Engine](/Software/Terminal_Event_Engine)

## Startup Position2x2

```mermaid
quadrantChart
x-axis "Manual / Fragmented" --> "Programmatically Integrated"
y-axis "Fixed / Opaque Pricing" --> "Priced per Lifecycle"
"Portyn": [0.85, 0.85]
"Project44": [0.80, 0.40]
"Legacy EDI connections": [0.65, 0.20]
"Manual terminal portal scraping": [0.15, 0.30]
```

## Startup Offer

**Proof**:
- Targeting 99% milestone completeness across the top North American port terminals
- Aiming to eliminate daily manual portal scraping for mid-sized freight forwarders
- Designed to reduce drayage detention fees by surfacing yard availability instantly
**Tiers**:
- Name: Pay-As-You-Go API · Price: ~$0.80–$1.50 per container · Inclusions: Full terminal event aggregation and standardized timeline generation for individual container lifecycles, billed purely on successful completion with no monthly minimums.
- Name: Volume Commitment · Price: ~$0.30–$0.60 per container · Inclusions: SLA-backed container lifecycles intended for teams processing 10,000+ TEUs monthly, including dedicated webhooks and access to historical yard timelines.
**Guarantee**: Portyn bills exclusively for complete container lifecycles; if a container reaches the gate but the timeline missed a critical terminal milestone due to our aggregation failure, tracking for that container is waived.
**Business Function**: ProvideService
**Objection Handlers**:
- Carrier EDI already provides milestone updates. -> Carrier EDI is typically delayed by 12 to 24 hours; Portyn targets direct terminal-level data to surface events precisely when they happen.
- Terminals constantly change their portals and break scrapers. -> Portyn is engineered to programmatically adapt to portal schema changes, absorbing the maintenance burden so your internal integrations never break.
- Why not just use Project44? -> Portyn focuses strictly on deep, granular terminal yard aggregation rather than broad ocean tracking, ensuring higher fidelity data specifically for drayage and gate operations.
- What if a container routes to an unsupported terminal? -> The API includes an endpoint designed to instantly verify yard coverage before initiating tracking, ensuring you only incur charges for containers we can actually trace.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Direct and authoritative, emphasizing operational certainty over technical jargon.
**Tagline**: Unify fragmented terminal yard events into standardized container timelines.
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: A heavy-duty visual system anchoring high-visibility safety yellow and tarmac black against stark, utilitarian typography reminiscent of shipping manifests.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: B2B → Freight Forwarders & Logistics Tech Providers → Beneficial Cargo Owners (Shippers)
**Gtm Motion**: Acquires logistics operations and engineering teams through self-serve API documentation for testing terminal visibility on individual containers. Expands accounts by shifting from ad-hoc container lookups to fleet-wide integration, driven by the predictability of the pure per-container-lifecycle pricing model.
**Agent Channel**: Designed to publish a structured OpenAPI schema in the LangChain tool registry and OpenAI's capability feed, allowing autonomous freight-dispatch and supply chain monitoring agents to discover and call the terminal timeline fetching tool.
**Primary Channel**: Organic developer search targeting high-intent queries like 'terminal yard event API' and 'automated EDI alternative for container tracking', driving technical logistics buyers directly to sandbox documentation.

## Startup Customer Journey

```mermaid
flowchart LR; A[API Documentation] --> B[Sandbox Environment]; B --> C[Container Timeline]; C --> D[Webhook Endpoints]; D --> E[Volume Commitment Tier]; E --> F[Autonomous Freight-Dispatch Agent];
```

## 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 API integration pilot with a regional drayage fleet tracking 500 containers, aiming to validate zero missed critical yard milestones and seamless webhook delivery.
- 60-day parallel testing phase alongside a high-volume forwarder's existing carrier EDI system, targeting conclusive proof of a 12-plus hour speed advantage in surfacing terminal container availability.
**Target Metrics**:
- Target: 99% milestone event completeness across the top North American port terminals.
- Target: 12-to-24 hour reduction in milestone data latency compared to standard carrier EDI feeds.
- Target: 100% elimination of daily manual portal scraping hours for mid-sized freight forwarding teams.
- Target: 20% reduction in average drayage detention fees through instant yard availability surfacing.
**Target Case Studies**:
- Mid-sized freight forwarder managing 5,000 TEUs monthly: Replacing a team of data entry clerks manually scraping individual port terminal portals with Portyn's Pay-As-You-Go API to automate container timeline generation.
- Regional drayage operator: Integrating Portyn's terminal event webhooks directly into dispatch software to surface yard availability instantly, targeting the elimination of detention and demurrage fees caused by delayed information.
- High-volume logistics provider processing 10,000+ TEUs: Switching from standard carrier EDI to Portyn's direct terminal aggregation to bypass 12-to-24 hour EDI delays and optimize daily gate appointment scheduling.
**Testimonial Targets**:
- VP of Operations at a freight forwarding firm expressing relief that their logistics coordinators no longer waste hours logging into multiple, frequently changing terminal websites to check container statuses.
- Lead Dispatcher at a drayage company confirming that Portyn's real-time yard updates allow them to secure gate appointments the minute a container becomes available, directly preventing demurrage charges.
- CTO of a logistics software provider stating that Portyn successfully absorbs the maintenance burden of broken terminal scrapers, allowing their internal engineering team to stop patching broken integrations.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Terminal operators block programmatic access or implement strict anti-scraping measures on their portals, immediately cutting off the primary data source. · Mitigation Status: unmitigated
- Severity: high · Description: Unpredictable terminal operating system updates break the event standardization logic, causing missed container lifecycle milestones and forcing revenue forfeiture. · Mitigation Status: in-progress
- Severity: high · Description: Charging exclusively per successful container lifecycle forces the company to absorb all infrastructure and compute costs during systemic port congestion or terminal data outages. · Mitigation Status: unmitigated
- Severity: moderate · Description: Incumbent supply chain visibility platforms leverage their carrier relationships to negotiate exclusive direct-API access with major port terminals. · Mitigation Status: in-progress

## Startup Competitors

- [Legacy EDI connections](/Competitors/Legacy_EDI_connections) — Status Quo
- [Manual terminal portal scraping](/Competitors/Manual_terminal_portal_scraping) — DIY
- [Project44](/Competitors/Project44) — Incumbent
- [FourKites](/Competitors/FourKites) — Incumbent
- [Vizion API](/Competitors/Vizion_API) — API Provider

## Startup Story Brand

**Hero**:
- **Need**: to be the logistics operator who knows, not the one who guesses
- **Want**: to eliminate daily manual terminal portal scraping for container status
- **Identity**: the drayage dispatcher at a mid-sized freight forwarding firm
**Plan**:
- Step: Verify coverage · Detail: Query the API to confirm terminal yard support before initiating tracking.
- Step: Review timelines · Detail: Access standardized container lifecycles that aggregate gate, rail, and yard milestones automatically.
- Step: Dispatch trucks · Detail: Use real-time yard availability to schedule pickups and avoid detention fees.
**Guide**:
- **Empathy**: Operational margins are won in the terminal yard — but portal schema changes and delayed EDI data break dispatch schedules daily.
**Problem**:
- **Villain**: portal fragmentation
- **External**: dispatchers waste hours logging into individual terminal websites to check yard availability and gate status because carrier EDI is delayed by 12 hours
- **Internal**: you feel blindsided by surprise detention fees and late-pickup penalties you can't defend
- **Philosophical**: Logistics expertise belongs in moving freight, not in refreshing browser tabs.
**Success**: Terminal data flows directly into your operations, surfacing yard availability instantly and eliminating the manual portal chase.
**One Liner**: What if terminal yard data was instant and standardized? Portyn aggregates fragmented terminal events into complete container timelines, eliminating manual portal scraping and surprise detention fees.
**Positioning**:
- **So That**: eliminate surprise detention fees and manual data entry
- **Unlike**: manual terminal portal scraping
- **For Whom**: mid-sized freight forwarders
- **Category**: Terminal yard event aggregation
**Call To Action**:
- **Direct**: Track a container
- **Transitional**: View the API schema
**Failure Stakes**:
- Surprise drayage detention fees
- Missed pickup windows
- Dispatcher burnout from manual scraping
**Transformation**:
- **To**: the terminal's logistics lead
- **From**: a dispatcher buried in manual portal scraping
**Controlling Idea**: Terminal data should be a utility, not a manual research project.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: What if terminal yard data was instant and standardized? Portyn aggregates fragmented terminal events into complete container timelines, eliminating manual portal scraping and surprise detention fees.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 291d91dfcada1c8a

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Terminal yard event aggregation for mid-sized freight forwarders. Unlike manual terminal portal scraping — eliminate surprise detention fees and manual data entry.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: f3599b34cf507cdf

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: dispatchers waste hours logging into individual terminal websites to check yard availability and gate status because carrier EDI is delayed by 12 hours
Solution: What if terminal yard data was instant and standardized? Portyn aggregates fragmented terminal events into complete container timelines, eliminating manual portal scraping and surprise detention fees.
Customer: mid-sized freight forwarders
Unlike: manual terminal portal scraping
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 28d8bf462889cedf

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

**Pain**: dispatchers waste hours logging into individual terminal websites to check yard availability and gate status because carrier EDI is delayed by 12 hours
**Metrics**: Target: Terminal data flows directly into your operations, surfacing yard availability instantly and eliminating the manual portal chase.
**Rendered**: Pain: dispatchers waste hours logging into individual terminal websites to check yard availability and gate status because carrier EDI is delayed by 12 hours
Economic buyer: Freight Forwarders & Logistics Tech Providers
Metrics: Target: Terminal data flows directly into your operations, surfacing yard availability instantly and eliminating the manual portal chase.
Competition: manual terminal portal scraping
**Mechanism**: spine-derived-v1
**Competition**: manual terminal portal scraping
**Economic Buyer**: Freight Forwarders & Logistics Tech Providers
**Vocab Fingerprint**: 0bc877eaef4284f5

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Terminal yard event aggregation for mid-sized freight forwarders

mid-sized freight forwarders — dispatchers waste hours logging into individual terminal websites to check yard availability and gate status because carrier EDI is delayed by 12 hours What if terminal yard data was instant and standardized? Portyn aggregates fragmented terminal events into complete container timelines, eliminating manual portal scraping and surprise detention fees.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 118ad1ceb0aaa204

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Terminal yard event aggregation. What if terminal yard data was instant and standardized? Portyn aggregates fragmented terminal events into complete container timelines, eliminating manual portal scraping and surprise detention fees. Serves mid-sized freight forwarders.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 8d0753997a83a860

## Neighborhood

### Candidate solutions

- [Open-Source Cannibalization](/Problems/Open-Source_Cannibalization) — candidate solution for · Problems
- [Delayed Unbilled Time Realization](/Problems/Delayed_Unbilled_Time_Realization) — candidate solution for · Problems
- [Hybrid Engine Retooling Costs](/Problems/Hybrid_Engine_Retooling_Costs) — candidate solution for · Problems

### Competitors

- [Manual terminal portal scraping](/Competitors/Manual_terminal_portal_scraping) — competes with · Competitors
- [Legacy EDI connections](/Competitors/Legacy_EDI_connections) — competes with · Competitors
- [Project44](/Competitors/Project44) — competes with · Competitors
- [Vizion API](/Competitors/Vizion_API) — competes with · Competitors
- [FourKites](/Competitors/FourKites) — competes with · Competitors
- [Thomson Reuters Practice CS](/Competitors/Thomson_Reuters_Practice_CS) — competes with · Competitors
- [BigTime](/Competitors/BigTime) — competes with · Competitors
- [CCH Axcess Practice](/Competitors/CCH_Axcess_Practice) — competes with · Competitors
- [Excel WIP Exports](/Competitors/Excel_WIP_Exports) — competes with · Competitors
- [Xero Practice Manager](/Competitors/Xero_Practice_Manager) — competes with · Competitors

### Embodies

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

### What it offers

- [Terminal Event Engine](/Software/Terminal_Event_Engine) — offers · Software
- [Exhaust Allocation Engine](/Software/Exhaust_Allocation_Engine) — offers · Software

### Composed of

- [Activity Telemetry SDK](/Agents/Activity_Telemetry_SDK) — composes · Agents
- [Proactive Billing Service](/Services/Proactive_Billing_Service) — composes · Services
- [Engagement Attribution Agent](/Agents/Engagement_Attribution_Agent) — composes · Agents
- [Context Matching Worker](/Agents/Context_Matching_Worker) — composes · Agents
- [Desktop Exhaust Engine](/Agents/Desktop_Exhaust_Engine) — composes · Agents

### Who it serves

- [Accounting Firm](/CompanyTypes/Accounting_Firm) — serves · CompanyTypes

### Similar Startups

- [Depotport](/Startups/Depotport) — similar · Startups
- [Cargovista](/Startups/Cargovista) — similar · Startups
- [Valleyrail](/Startups/Valleyrail) — similar · Startups
- [Axiomquay](/Startups/Axiomquay) — similar · Startups
- [Coordinatortower](/Startups/Coordinatortower) — similar · Startups
- [Voyagepoint](/Startups/Voyagepoint) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Tracelane](/Startups/Tracelane) — similar · Startups
- [Cadencevessel](/Startups/Cadencevessel) — similar · Startups
- [Conduitharbor](/Startups/Conduitharbor) — similar · Startups
- [Truewharf](/Startups/Truewharf) — similar · Startups
- [Depotquay](/Startups/Depotquay) — similar · Startups
- [Crossoyage](/Startups/Crossoyage) — similar · Startups
- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Basisyard](/Startups/Basisyard) — similar · Startups
- [Cargowharf](/Startups/Cargowharf) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Beamlane](/Startups/Beamlane) — similar · Startups
- [Coordinatyard](/Startups/Coordinatyard) — similar · Startups