we <3 open source

MIT licensed, and the repository is the real one.

There is no separate internal version of Teleprompt. The hosted instance exists so that people who do not want to run infrastructure do not have to.

The licence

Teleprompt is released under the MIT licence. In plain terms: use it commercially, modify it, redistribute it, build a product on it. Keep the copyright notice, and accept that it comes with no warranty.

MIT License

Copyright (c) 2026 Biios

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Why it is open

Teleprompt was built at Biios because founder videos and launch films kept needing a prompter that a second person could drive, and the options were either a hardware rig or an app with a subscription attached to a scroll bar.

Once it existed, keeping it private would have meant maintaining a tool nobody could improve. So it is given to the community as it is used internally: same code, no held-back tier.

Standing on

Teleprompt is a thin layer over a lot of other people’s work. The significant pieces, and what each is doing here:

ProjectLicenceDoing what
Next.jsMITApp Router, RSC, the build
ReactMITThe interface
TypeScriptApache-2.0The whole codebase
tRPCMITTyped client-server calls
TanStack QueryMITClient cache
Tailwind CSSMITThe design tokens
Drizzle ORMApache-2.0Schema and queries
Auth.jsISCGoogle and GitHub sign-in
supabase-jsMITThe realtime channel
ZodMITEvery trust boundary
@uiw/react-md-editorMITThe Markdown editor
react-markdownMITRendering blocks
Phosphor IconsMITIconography
Familjen Grotesk, Plus Jakarta Sans, JetBrains Mono, Bebas NeueSIL OFL 1.1Typography

Contributing

Issues and pull requests are welcome. The contributing guide covers the repository layout, the conventions, and how to test a sync change properly, which needs two real devices, because the interesting parts cannot be exercised in one browser window.

biios

We partner with ambitious founders to build, scale and grow businesses that create real impact.