I built an open-core logistics platform — here's what happened in month 1
Hey IH,
I've been working on Norynth Logistics — an API-first SaaS platform for freight intelligence. Open-core model: foundational features free, advanced features usage-based.
What we built:
• FleetOS — programmable fleet management
• RouteIQ — route optimization engine (Rust)
• TrackNet — real-time tracking across 850+ carriers
• FreightAPI — unified carrier API
Why logistics? Most logistics software is closed, expensive, and built for dashboards first. Developers building logistics features have to either use clunky APIs or build from scratch. We went API-first from day one.
The stack:
- Core API: PHP with RoadRunner (async)
- Route optimization: Rust (sub-200ms responses)
- Real-time tracking: Go + WebSockets
- SDKs: PHP, Python, Go, Node.js, Rust
- Docs: OpenAPI 3.0 + Redoc
Metrics so far (month 1):
- Page load: ~0.8s
- Lighthouse: 96 Performance
- First leads: 3 enterprise inquiries
- Open-source GitHub stars: growing organically
Biggest lesson: Building-in-public works. Posting architecture decisions on LinkedIn got more traction than any feature announcement. Developers want to see how it's built, not just what it does.
What I'd love feedback on:
- Does open-core for logistics make sense to you?
- Any features you'd expect that aren't listed?
- The pricing model — free tier for basics, usage-based for scale. Fair?
Try it yourself:
👉 https://logistics.norynth.com
Read the full architecture deep-dive on Medium:
Happy to answer any technical questions. I built the SDKs myself — ask me anything.
This is a strong direction because the developer angle in logistics is still underbuilt. Most freight tools feel dashboard-first, while the real pain for teams building logistics products is carrier data, tracking, route logic, SDKs, and APIs that do not feel painful to integrate.
The open-core angle also makes sense here if the free layer helps developers start building quickly, and the usage-based layer maps to real volume once teams hit scale. The 3 enterprise inquiries in month one are a good signal that the infrastructure pain is real.
One thing I would pressure-test early is the brand architecture. Norynth Logistics is clear, but FleetOS, RouteIQ, TrackNet, and FreightAPI already make this feel like a broader logistics infrastructure stack, not just one logistics SaaS product.
If this becomes API-first freight infrastructure for developers, the name may need to carry more technical weight before docs, SDKs, GitHub memory, and enterprise conversations lock in.
Davoq .com would fit that direction well because it feels like hard infrastructure, not a dashboard tool. It could carry carrier APIs, route optimization, tracking, SDKs, and logistics automation under one stronger developer-facing brand.