|3 months ago|
|.github||4 months ago|
|.vscode||3 months ago|
|build||4 months ago|
|config||3 months ago|
|controllers||3 months ago|
|core||3 months ago|
|doc/api||5 months ago|
|examples||7 months ago|
|geoip||7 months ago|
|logging||4 months ago|
|metrics||6 months ago|
|models||4 months ago|
|router||3 months ago|
|static||7 months ago|
|test||4 months ago|
|utils||4 months ago|
|webroot||3 months ago|
|yp||3 months ago|
|.editorconfig||1 year ago|
|.gitattributes||5 months ago|
|.gitignore||3 months ago|
|.golangci.yml||10 months ago|
|.prettierignore||7 months ago|
|CODE_OF_CONDUCT.md||1 year ago|
|Dockerfile||3 months ago|
|LICENSE||1 year ago|
|README.md||8 months ago|
|forest-notes.md||3 months ago|
|go.mod||3 months ago|
|go.sum||3 months ago|
|main.go||4 months ago|
|nsswitch.conf||3 months ago|
|openapi.yaml||3 months ago|
|pkged.go||3 months ago|
In 2020 the world changed when everyone become stuck in their homes, looking for creative outlets to share their art, skills and themselves from inside their bedroom.
This created an explosion of live streaming on Facebook Live, YouTube Live, Instagram, and Twitch. These services provided everything they needed, an easy way to live stream to the world, and a chat for users to be a part of their community.
That's when I wanted a better option for people. Something you could run yourself and get all the functionality of these services, where you could live stream to an audience and and allow them to take part in the chat, just like they've been used to on all the other services. There should be a independent, standalone Twitch in a Box.
Keep in mind that while streaming to the big social companies is always free, you pay for it with your identity and your data, as well as the identity and data of every person that tunes in. When you self-host anything you'll have to pay with your money instead. But running a self-hosted live stream server can be done for as cheap as $5/mo, and that's a much better deal than selling your soul to Facebook, Google or Amazon.
The goal is to have a single service that you can run and it works out of the box. Visit the Quickstart to get up and running.
Many aspects can be adjusted and customized to your preferences. Read more about Configuration to update the web UI, video settings, and more.
Owncast includes a web interface to your video with built-in chat that is available once you start the server.
Read more about the features provided and how to configure them in the web documentation.
In general Owncast is compatible with any software that uses
RTMP to broadcast to a remote server.
RTMP is what all the major live streaming services use, so if you’re currently using one of those it’s likely that you can point your existing software at your Owncast instance instead.
OBS, Streamlabs, Restream and many others have been used with Owncast. Read more about compatibility with existing software.
Two ways of storing and distributing the video are supported.
This is the simplest and works out of the box. In this scenario video will be served to the public from the computer that is running the server. If you have a fast internet connection, enough bandwidth alotted to you, and a small audience this may be fine for many people.
Instead of serving video directly from your personal server you can use a S3 compatible storage provider to offload the bandwidth and storage requirements elsewhere.
git clone https://github.com/owncast/owncast
go run main.go pkged.gowill run from source.
There is also a supplied
Dockerfile so you can spin it up from source with little effort. Read more about running from source.
The admin ui is built at: https://github.com/owncast/owncast-admin it is bundled into the final binary using pkger.
To bundle in the latest admin UI:
go install github.com/markbates/pkger/cmd/...
go run main.go pkged.go
Distributed under the MIT License. See
LICENSE for more information.
Project chat: Join us on Rocket.Chat if you want to contribute, follow along, or if you have questions.
Project Link: https://github.com/owncast/owncast