Launch
Gortex
Visit
Example Image

Gortex

Decisioning infrastructure API for consumer platforms

Visit

Gortex is a ranking and monetization API for social feeds, marketplaces, creator platforms, dating apps, and job boards. Send a user, a surface, and a set of candidates to one endpoint, and Gortex returns them ranked with sponsored slots filled in under 200ms p99. Engineering teams use it in place of building and maintaining a separate ranking engine and ad server.

Example Image
Example Image
Example Image
Example Image

Features

  • One API call (POST /v1/decide) returns a ranked feed and fills sponsored slots in the same response
  • Sub-200ms p99 latency, built to sit between candidate generation and what users see
  • Per-user ordering: each recipient gets their own ranked list for each surface
  • Sponsored slots are priced against the organic order, so a paid item only takes a slot when the placement fits
  • Decision and trace IDs on every response, so you can see why each item landed where it did
  • Calibrated linear ranking and deterministic sponsored slot-filling, live today
  • OpenAPI 3.1 spec with seven typed SDKs
  • Progressive integration ladder: start with plain REST (L0) and adopt deeper integration levels over time

Use Cases

  • Social and creator platforms: rank a personalized “For You” feed and add sponsored posts without degrading feed quality
  • Marketplaces: order listings per buyer and run sponsored listings next to organic results in one call
  • Dating apps: break the popularity loop where a few profiles get most of the attention, with per-user ordering instead of hand-tuned weights
  • Ecommerce and drops: rank products and fill paid placements fast enough for high-traffic launches
  • Content discovery apps: stop showing every user the same feed by personalizing the order per user
  • Job boards, travel, and food delivery: rank results and monetize top positions with one ranking API
  • Engineering teams weighing build vs. buy: replace an in-house ranking and ad-slot system with one API, keeping decision traces for debugging and audits

Comments

Hi Fazier, I’m Hemin, founder of Gortex. Every consumer platform with a feed eventually hits the same two questions: what should each user see first, and where do sponsored items go without making the feed worse? Most teams answer them with two separate systems, a ranker and an ad server, and then spend years writing glue code to keep them from fighting each other. We built Gortex to make that one decision instead of two. You send a recipient, a surface, and your candidates. One API call returns the ranked order with sponsored slots already filled, in under 200ms p99. A paid item only takes a slot when the placement fits against the organic order, and every response carries a decision ID so you can trace why each item landed where it did. To be clear about where we are: today ranking is calibrated linear and slot-filling is deterministic. We’re in invite-only private beta, working with marketplaces, social and creator apps, dating apps, and discovery products. A question for anyone who has built this in-house: how did you decide where sponsored items were allowed to go in your feed? I’d love to hear what worked and what you’d never do again.

Premium Products
Social Links

Comments

Hi Fazier, I’m Hemin, founder of Gortex. Every consumer platform with a feed eventually hits the same two questions: what should each user see first, and where do sponsored items go without making the feed worse? Most teams answer them with two separate systems, a ranker and an ad server, and then spend years writing glue code to keep them from fighting each other. We built Gortex to make that one decision instead of two. You send a recipient, a surface, and your candidates. One API call returns the ranked order with sponsored slots already filled, in under 200ms p99. A paid item only takes a slot when the placement fits against the organic order, and every response carries a decision ID so you can trace why each item landed where it did. To be clear about where we are: today ranking is calibrated linear and slot-filling is deterministic. We’re in invite-only private beta, working with marketplaces, social and creator apps, dating apps, and discovery products. A question for anyone who has built this in-house: how did you decide where sponsored items were allowed to go in your feed? I’d love to hear what worked and what you’d never do again.

Premium Products