Mashery

Mashery
Name	Mashery
Type	Subsidiary
Industry	Software industry
Founded	2006
Founder	Jayant Kadambi, Aditya Khanna, Vishwanath
Headquarters	San Francisco, California
Area served	Global
Parent	Intel Corporation (acquired 2013), later Tibco Software (acquired 2015)

Mashery

Mashery was an enterprise software company that provided application programming interface (API) management and gateway services to corporations and developers. It operated in the ecosystem of cloud computing, platform services, web APIs, and developer portals, offering tools for API lifecycle, monetization, analytics, and security. Mashery’s platform was used by technology firms, media companies, telecommunications providers, and public sector agencies to expose, protect, and measure APIs within broader digital strategies driven by companies such as Google, Facebook, Twitter, Microsoft, Amazon.com and telecommunication operators.

Overview

Mashery positioned itself within the Software as a Service market and the emerging API management sector alongside firms like Apigee, Akana, WSO2, MuleSoft, Kong (software), and 3scale. The company offered an API gateway, developer portal, analytics dashboards, key management, rate limiting, and policy enforcement to support partners including publishers, identity providers, payment platforms, and cloud vendors. Its services sat at the intersection of platform strategies pursued by companies such as Salesforce, LinkedIn, PayPal, Stripe (company), and media platforms including The New York Times and PewDiePie-adjacent networks.

History

Mashery was founded in 2006 during a wave of platformization following the rise of Amazon Web Services and the release of web APIs by firms like Flickr and eBay. Early customers included startups and media companies adopting programmatic distribution channels exemplified by platforms such as Apple Inc.’s ecosystem and Google Maps API. In 2011–2013 the API economy accelerated with initiatives by ProgrammableWeb and industry events like Strata Conference and API World, and Mashery expanded through partnerships with systems integrators and telecommunication vendors including Verizon Communications and AT&T. In 2013 Mashery was acquired by Intel Corporation as part of Intel’s strategy to address edge computing and Internet of Things use cases alongside projects such as Intel IoT Platform. In 2015 Mashery changed ownership when TIBCO Software acquired the unit to integrate with enterprise integration products including TIBCO Rendezvous and TIBCO ActiveMatrix.

Products and Services

Mashery’s product suite encompassed API gateway functions, developer onboarding, API monetization, and analytics. Key offerings enabled API publishers to provide developer registration, API key issuance, OAuth token support (compatible with OAuth 2.0 implementations used by Facebook Login and Google Identity), quota management, and SLA enforcement used by enterprises such as Adobe and eBay. The developer portal components paralleled communities around GitHub, Stack Overflow, and documentation practices popularized by Stripe (company) and Twilio. Analytics features reported traffic, latency, errors and revenue metrics in ways familiar to teams using New Relic, Splunk, and Datadog for observability. Professional services included onboarding, API design consulting influenced by approaches from RESTful API design advocates and tooling ecosystems like Swagger (now OpenAPI Specification) and RAML.

Technology and Architecture

Mashery’s architecture combined a cloud-hosted control plane with distributed gateways that could be deployed on-premises, in colocation facilities, or within cloud providers such as Amazon Web Services, Microsoft Azure, and Google Cloud Platform. It integrated policy engines for authentication and authorization compatible with standards promoted at IETF and implementations by identity vendors like Okta and Auth0. The gateway processed request/response transformations, protocol mediation between SOAP backends and RESTful frontends, caching, traffic shaping, and TLS termination similar to reverse proxy solutions like NGINX and HAProxy. Telemetry and logging were exposed to analytics pipelines often integrated with event systems such as Apache Kafka and data warehouses exemplified by Snowflake or Amazon Redshift for downstream business intelligence.

Customers and Use Cases

Mashery served media companies, technology platforms, telecoms, financial services firms, and public institutions. Typical use cases included developer ecosystems for content distribution at organizations like The Weather Company and publisher APIs resembling efforts by The Guardian and BBC. Telecommunications use cases mirrored initiatives at Verizon and AT&T to monetize network capabilities and provide developer platforms. Financial services customers integrated with payment rails and identity systems similar to Visa and Mastercard for secure transaction APIs. Public sector agencies used API management to enable open data programs comparable to Data.gov and municipal portals.

Business Model and Partnerships

Mashery operated on subscription and tiered pricing for API traffic, support SLAs, and professional services, echoing commercial models used by firms such as Salesforce and Microsoft Azure Marketplace listings. Strategic partnerships included systems integrators like Accenture, Deloitte, and Capgemini for large-scale API programs, and cloud partnerships with Amazon Web Services, Microsoft, and Google for hosting and distribution. Technology alliances extended to identity and security vendors including Okta and Symantec as well as developer community platforms like GitHub and API directories such as ProgrammableWeb.

Security and Compliance

Security features emphasized OAuth flows, API key management, rate limiting to mitigate denial-of-service scenarios referenced in incidents involving Dyn (company) and others, and TLS encryption practices endorsed by IETF standards. Compliance efforts supported frameworks and certifications sought by enterprises, aligning with audit regimes like SOC 2 and data protection statutes influenced by General Data Protection Regulation requirements applicable to cross-border API data flows. Integrations with identity providers and web application firewalls mirrored controls used by Cloudflare and Imperva to provide layered defense-in-depth for API surfaces.

Category:Application programming interfaces