# Stainless Code
> Open-source TypeScript and JavaScript libraries with sharp contracts — tooling for modern apps and AI-agent workflows.
# About
Source: https://stainless-code.com/about
We ship libraries, not a platform.
Stainless Code is the GitHub org and company hub behind open-source TypeScript and JavaScript tooling for modern apps and AI-agent workflows. This site indexes those libraries and states how we ship. Product guides stay on each library’s own docs.
## Why Stainless Code
1. **Sharp contracts** — Public APIs you can pin and reason about.
2. **Independent libraries** — Pick what you need. MIT-licensed, no forced stack.
3. **Built for agents too** — Machine-readable docs and predictable packages where agents work.
## Hub vs product docs
This domain root is the **company index**: pitch, catalog, and outbound links. Each flagship library owns its docs tree:
| Product | Docs |
| ------- | ---- |
| Codemap | [stainless-code.com/codemap](https://stainless-code.com/codemap) |
| Persist | [stainless-code.com/persist](https://stainless-code.com/persist) |
| Layers | [stainless-code.com/layers](https://stainless-code.com/layers) |
| Lossless | [stainless-code.com/lossless](https://stainless-code.com/lossless) |
Full one-liners, npm packages, and legacy utilities: [product index](/products).
## How we ship
- Source and issues live under the [stainless-code](https://github.com/stainless-code) GitHub org.
- Packages are typically MIT — confirm in each repo’s license file.
- Prefer agent-readable docs (`llms.txt`) and clear package contracts over sprawling frameworks.
- Want to help? Open an issue or PR on the relevant product repo. There is no separate company contribution guide beyond each library’s docs.
## People
Today Stainless Code is founded and maintained by one person — see [Team](/team). Selected companies and products in the founder’s background: [Experience](/experience). Company and partnership questions: [Contact](/contact).
## FAQ
---
# Contact
Source: https://stainless-code.com/contact
Two channels, depending on the ask.
## Open source
Bugs, features, and PRs belong on the relevant product repo under [github.com/stainless-code](https://github.com/stainless-code) — for example Codemap, Persist, Layers, or Lossless. Prefer an issue on that repo over a general ping.
## Company & partnerships
For commercial questions, sponsorship, or partnerships:
**[sebastian.sutu@stainless-code.com](mailto:sebastian.sutu@stainless-code.com)**
Short message with context is enough. Also: [GitHub](https://github.com/SutuSebastian), [LinkedIn](https://www.linkedin.com/in/sutu-jeanu-sebastian/), [X](https://x.com/sutusebastian), [Bluesky](https://bsky.app/profile/sutusebastian.bsky.social).
Who’s behind the org: [Team](/team). Background: [Experience](/experience).
---
# Experience
Source: https://stainless-code.com/experience
Track record for the founder, under **Sutu Sebastian** — employment, freelance, and open-source maintainership. Includes work from before Stainless Code existed. This is not a Stainless Code customer logo wall.
## How this relates to Stainless Code
OSS libraries under Stainless Code are separate from client delivery. Company and partnership questions: [Contact](/contact). Who ships the org today: [Team](/team).
---
# Products
Source: https://stainless-code.com/products
Need a structural index for agents, hydration-aware store persistence, awaitable overlays, or lossless context management? Start from the catalog below. Why we ship this way: [About](/about).
## Libraries
| Product | One-liner | Docs | npm |
| ------- | --------- | ---- | --- |
| **Codemap** | Local SQLite index for agents — SQL and recipes instead of scanning the tree | [docs](https://stainless-code.com/codemap) | [`@stainless-code/codemap`](https://npmx.dev/@stainless-code/codemap) |
| **Persist** | Any store, any storage — one middleware, no hydrate flash | [docs](https://stainless-code.com/persist) | [`@stainless-code/persist`](https://npmx.dev/@stainless-code/persist) |
| **Layers** | Headless modal/dialog/drawer/popover/toast manager — open any layer from anywhere | [docs](https://stainless-code.com/layers) | [`@stainless-code/layers`](https://npmx.dev/@stainless-code/layers) |
| **Lossless** | Lossless context management for coding agents — aged history becomes summary pointers, every message stays verbatim and searchable | [docs](https://stainless-code.com/lossless) | `pi-lossless` · `lossless-core` |
## When to reach for each
- **Codemap** — Use when an agent (or tool) needs a local structural map of a codebase — symbols, imports, and calls — as SQL and recipes instead of scanning the tree.
- **Persist** — Use when a reactive store needs hydration-aware persistence across storage backends — one middleware, no flash of empty state.
- **Layers** — Use when overlays should open from anywhere as awaitable calls on a named stack — headless core plus framework adapters, not ad-hoc dialog state.
- **Lossless** — Use when agent sessions outgrow the context window — aged history becomes summary pointers while every message stays verbatim and searchable.
Different problems. No forced stack — pick one package or several.
## Legacy / adjacent
Older React utilities under the same org (npm-homed; no dedicated docs site today):
- [`@stainless-code/react-custom-events`](https://npmx.dev/@stainless-code/react-custom-events)
- [`@stainless-code/react-paginate`](https://npmx.dev/@stainless-code/react-paginate)
- [`@stainless-code/react-memo`](https://npmx.dev/@stainless-code/react-memo)
Archive / npm links — not the primary product index.
---
# Team
Source: https://stainless-code.com/team
Stainless Code is a one-person open-source shop today. Libraries ship under the [stainless-code](https://github.com/stainless-code) GitHub org; product docs stay on each library’s site.
## People
## Background
Selected companies and products — SoftState, Flowbite React, Streamlyne, Paybilt, earlier Ledidi, and more — on [Experience](/experience).
## Working with us
Open-source work happens in public on GitHub. For company or partnership questions, see [Contact](/contact).