Open Source Software
Open source is how we build ZanReal. We maintain the packages our own products run on, and when someone here has time to spare it goes into the projects we depend on: making them faster, fixing their docs and sites, shipping the work their maintainers never get to.
Projects
What we build and keep alive: libraries, developer tools, the occasional web app. We publish them, version them and answer the issues.
@zanreal/search
Fuzzy search over TypeScript objects, with no schema to declare.
Vercel OSS Directory
A browsable directory of the Vercel Open Source Program.
@zanreal/devcontainer
A batteries-included dev container image for TypeScript projects.
All our docs
Reference and guides for every package we publish.
Program
OSS Partner ProgramNo contract, no schedule, no account manager. When someone on the team has time, they take something off your backlog and fix it. You get a pull request and decide whether it lands.
Our people's time
Whoever is free that week picks the work up and does it. If a review or a second opinion is what you need instead, that works too.
The scope you pick
The package, the docs, the website or the release process, whichever you name.
Skills on loan
Performance, frontend, documentation sites, builds and deployment, TypeScript. Whatever the person with time happens to be good at.
Yours to keep
Everything lands in your repository under your licence, and we stay reachable after it merges.
How it works
Three steps. No contract, no deadline, no invoice at the end.
- 01
Send us the repository
One short form: a link to the repository and the thing you have been putting off since spring.
- 02
We tell you what we would do
What we want to change, how much of your time the review will take, and what we expect to improve. If it is not worth doing, we say so.
- 03
You decide what lands
The work arrives as a pull request and your team reviews it like any other. Nothing reaches the project without your approval.
Who should apply
To be considered for the program, projects must...
Be truly open source. An OSI-approved licence, with development happening in the open.
Be alive. Recent commits, answered issues, releases that still ship.
Have users to lose. Other projects, companies or products depend on it.
Pick a number with us. One metric agreed up front and checked after the work lands, like downloads, docs traffic, load time or bundle size.
Stay in the loop. Review what we send, merge it, and tell us when we are wrong.
Have a code of conduct. Our people are joining your community.
Where we helped
Projects from the program. The card goes to the project site, the bar under it to the repository.
Work
The first delivery under the program: 1,100 documentation pages that stopped calling a function on every visit.
Valibot and Formisch: 1,100 docs pages served from cache instead of a function.
- Qwik
- TypeScript
- Vite
- Static Site Generation
- Sharp
Questions
What maintainers most often ask before sending us a repository. If something is missing here, just write to us.
Let us take it off your list.
Apply to the programSend us the repository and tell us what you keep putting off. We come back with a plan, or an honest no.
Can't keep up with changes in AI world?
Let us do the heavy lifting. Every week we distill the most important AI developments into a focused 5-minute briefing - so you stay ahead without the noise.
Find out more