Multi-carrier shipping API and dashboard for ecommerce businesses
Shippo gives ecommerce merchants, marketplaces and platforms one API and dashboard to rate, label, track and return shipments across carriers. Its polyglot stack (Python, Go, Ruby, Java, .NET, Phoenix) on Kubernetes and Kafka points to a carrier-integration estate built over many years, and job posts focus on cutting carrier launch time and integration friction. MCP in the stack and an MCP product owner role signal a push toward AI-agent access to shipping.
Shippo, founded in 2013 and headquartered in San Francisco, builds shipping software for ecommerce businesses, marketplaces and platforms. Customers connect to multiple carriers worldwide through a single API and dashboard to compare rates, print labels, automate international customs documents, track packages and manage returns. The privately held company employs 201–500 people and operates from San Francisco and Austin, with current hiring in the United States and Brazil. Its core specialties span multi-carrier shipping, shipment tracking and global shipping software.
Shippo runs React, Python, Go, Ruby on Rails, Django, Java and .NET services on Docker, Kubernetes and Istio, with Kafka, PostgreSQL, Redis and Elasticsearch, across AWS, GCP and Azure, plus dbt and Looker for data.
Yes. Hiring is accelerating and centers on engineering, with support, data and product roles too, skewing senior and principal. Openings are in the United States and Brazil.
Shippo is building a carrier integration platform, advancing its API platform roadmap, owning an MCP product, adding intelligent web app capabilities and connecting application services to ML systems.
Other companies in the same industry, closest in size
Shippo's technology stack, projects, and hiring signals are inferred from public hiring and company data — career pages, public listings, and company web presence — then clustered and de-duplicated. Figures are estimates that refresh over time. Read our full methodology →
This is not an official vendor or customer list. It is a technology-adoption signal inferred from public data, intended for B2B research.