Ethos
Built to last.
We want SavePoint to become one of the best broadcasting tools available to the entire world.
That goal shapes how we think about quality, reliability, durability, and long-term trust. We want SavePoint to be serious software that communities, hobbyists, curators, and station operators can depend on as part of their ongoing cultural life.
If we are going to ask people to build around SavePoint, then SavePoint has to earn that role.
Platform aware.
Platforms have become ecosystems where creators meet viewers, and simulcasting has gone from a niche workflow to a common practice. A creator who used to publish in one place now broadcasts to many at once, with each platform carrying its own audience, its own protocols, and its own pace of change.
SavePoint manages the broadcast pipeline behind that work. Schedule management and platform routing are two of its biggest feature areas, and absorbing them lets platforms like YouTube, Twitch, Kick, and TikTok stay focused on what they do best: platforming creator content and helping communities form around it.
We take the major streaming platforms seriously, and we watch the new ones as they emerge. Every platform SavePoint can broadcast to expands the reach of the creators who use it, and expanding that reach for creators worldwide is one of the reasons SavePoint exists.
Performers and attendees create together.
A station becomes more than a stream when listeners recognize its rhythm, voice, and character. Through dependable schedules, recurring programming, and familiar contributors, the station and its audience develop a shared experience that strengthens the station's identity over time.
We care about the systems behind that relationship.
SavePoint is being developed to give station owners intuitive management tools that connect programming, contributors, and audience experience. We want to help stations remain recognizable, engaging, and alive while strengthening the relationship between the people running them and the listeners who return.
Teamwork breathes life into the station.
Many tools are built around a single operator. One account, one session, one person at the center of everything. That model works for some use cases, but it is too limiting for many of the spaces we care about.
We believe communities should be able to share responsibility for keeping a station alive. Different contributors, different curators, different schedules, different roles, and a structure that does not collapse when one person steps away. A healthy station can be collaborative without becoming chaotic. It can be persistent without demanding constant manual heroics.
SavePoint is meant to support that kind of stewardship.
A station cannot become meaningful if it cannot become dependable.
We treat reliability as part of the value itself. A reliable system respects the effort of the people running it and the expectations of the people returning to it. It makes continuity believable.
User experience is part of reliability. We put enormous effort into making SavePoint intuitive and powerful, with a large share of our time going into performance optimization. We want operators to reach further, run with high uptime, and do as much as possible on limited compute. Fast and efficient software is how reliability shows up day to day.
Agency is a feature.
Giving users more control is the point. Capability, custody, and continuity make stations stronger, contributors more independent, and communities more durable. We build from the position that agency is a feature, and software that respects it does more for creators than software that second-guesses them.
That does not remove responsibility from the user. People remain responsible for operating within the legal, ethical, licensing, rights, and platform frameworks that apply to them. SavePoint is not a substitute for that responsibility.
People who care enough to keep something alive.
That includes hobbyists, station operators, niche communities, curators, creators, and builders who want more than a one-off live moment. People who want continuity. People who want shared structure. People who want a station to feel like a place, not just an event.
We think those users deserve serious tools.
We do not think robust station management should belong only to the largest broadcasters or the most heavily funded organizations. Some of the most important culture begins in small communities with strong taste, recurring presence, and enough structure to endure.
Built to cross borders.
We want SavePoint to be usable by creators and communities anywhere in the world. That means we treat translation and localization as core work, not an afterthought.
The website receives the same level of care in every supported locale. Inside the desktop application, multi-language support is still a work in progress, and we keep expanding it with every release as we build on our initial version.
The website is currently published in the languages shown below.
Currently supported languages
For additions and updates to language support, check our release notes and blog changelogs. If a language you care about is not yet supported, we would love to hear about it.
Built to run on major operating systems.
Creators do not all live in the same operating system. Building serious desktop software means meeting people where they are.
We chose an Electron and Node based foundation so that a single SavePoint codebase can reach the three operating systems where most desktop users live: Windows, macOS, and Linux. That choice lets the product grow across platforms without fragmenting into parallel rewrites.
Windows shipped first as an Electron desktop app. A command-line install now brings SavePoint to macOS, Linux, and WSL using the same broadcast engine, so wherever you operate your station from, there is an install path for it.
Target platforms
Every creative needs a channel.
A channel is infrastructure. It is the stable, curated place your community returns to because it is always running, and because the operator decides what plays. Running one is a craft of its own: scheduling segments, building playlists, opening slots to contributors, and shaping how the station sounds over time.
SavePoint Station Manager builds that channel for every kind of creator, from the solo artist to the Discord admin running a 24/7 community station. The station persists across the week, distributes to multiple platforms at once, and accepts live takeovers from any sub-account who holds a stream key. The operator runs it on their own hardware and leans on AI tooling for the production work that used to take a small team.
Every creator deserves a channel they own.
A future of inhabited stations.
More people should be able to run stations with confidence, with stronger custody over how their broadcast presence is managed and distributed. The station itself should be easier to sustain across contributors, schedules, and platforms.
Continuity should become more practical, participation more durable, and the internet should host more spaces that feel inhabited, ongoing, and intentionally operated.
SavePoint exists to help make that future real, and to do it with software that is worthy of becoming one of the best in the world.