experiential

experientiallabs/experiential

Experiential is the open source, zero markup gateway for BYOK, self-hosted and 1000+ marketplace models. It learns from your traffic to cut costs, recommend better models, and train a specialized model you own.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 25, 2026
today
Ship score
64/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
12.8K
Forks
263
Open issues
149
Watchers
14
Primary language
Python
Created
Jun 24, 2026
Owner
experientiallabs · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 113 startups in the directory ship primarily in Python.

Topics

This repository has no GitHub topics.

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Oct 25, 2026 — os_startup 98%, self-hostable 92%, hosted offering 57%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-10-25, found by the weekly discovery job at confidence 0.97. Answered by jev-1.14.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-25This is the badge for experientiallabs/experiential, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/experientiallabs/experiential.svg)](https://ossean.com/experientiallabs/experiential)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.