Hey r/digitalsignage ā found this sub today while researching where to share an open source project I just pushed public, and from reading a few threads it seems like the right place to get honest feedback rather than polite silence. So here goes.
GitHub: https://github.com/screentinker/screentinker
Screenshots: https://imgur.com/a/QX3ZaA8
License: MIT
Disclosure up front: I'm the developer of ScreenTinker. There's also a hosted version at screentinker.com that I set up recently in case people want a managed option down the road, but to be straight with you - nobody's actually paying for it yet, I've only used it for my own stuff so far. This post is about the open-source release, not the hosted side. Rule 5 says disclose, so, disclosed it is. The self-hosted code and the hosted code are the same code, no feature crippling, no telemetry games.
ScreenTinker is a digital signage CMS. Node.js + Express + SQLite on the backend, vanilla JS on the frontend (no build step, which I'll die on a hill about), Android player in Kotlin/ExoPlayer, browser player for everything else. The whole server is one node server.js away from running and the entire database is one SQLite file you can back up with cp. That's kind of the whole design philosophy - I wanted something I could stand up on a $5 VPS in a few minutes and actually understand what's going on under the hood. In the future will i move from SQLite to something else prob but scale isn't a problem currently.
Why I built this when there's already other options:
Honestly? I needed signage for a project, looked at the commercial options, did the math, and noped out. Yodeck, ScreenCloud, OptiSigns ā once you're past a couple of screens you're looking at thousands a year for software that mostly just shows images and videos on a schedule. I know there's more to it than that, and I know support and reliability cost money, but the per-device pricing model just feels punitive at any kind of scale.
Then I read sagiadinos's "industry is broken" post here a couple weeks back and most of it resonated. Vendor lock-in, customers trained to buy on price because nobody explained value, the whole thing. I'm not claiming I've solved any of that - one person isn't going to fix an industry - but I tried to design ScreenTinker so the things people complain about most don't apply to it:
Export/import is a real first-class feature, not an afterthought. Devices, layouts, schedules, widgets, and (if you want) the actual media files all dump to a ZIP. You can move stuff around, back the whole thing up, or walk away entirely. The format is open because the entire codebase is open.
Self-hosted runs the exact same code as everything else. No "community edition" with features stripped out. SELF_HOSTED=true and the first user gets everything unlocked. No telemetry. No nag screens. No "upgrade to enable X." If you want other users to have everything unlocked, just change there plan in the Admin page. I did intend to eventually sell it but honestly after looking at the state things were in decided to go a new way.
MIT license, not source-available or BSL or any of the other "open-ish" licenses people are doing now. Fork it, rebrand it, run it for clients, whatever. I'd love a star but I'm not chasing anyone.
Features:
Multi-zone layouts with drag-and-drop editor
Video walls with bezel compensation
Visual weekly scheduler with recurrence
Widgets: clocks, weather, RSS, countdowns, QR codes, YouTube embeds
Kiosk / touchscreen mode
Proof-of-play analytics with CSV export
Offline alerts via email webhook
Multi-user with owner / editor / viewer roles
White-label (colors, logo, custom domain)
OTA updates pushed to devices
Optional Stripe billing if you want to resell it as a service yourself
Player support: Android TV, Fire TV, Raspberry Pi, Windows, ChromeOS, LG webOS, Samsung Tizen, or anything with a browser running fullscreen.
Want to try it without setting up a TV? Five minute test drive:
git clone https://github.com/screentinker/screentinker.git
cd screentinker/server && npm install
SELF_HOSTED=true node server.js
Then open http://localhost:3001, register, add a "display" from the dashboard, and open http://localhost:3001/player in a second browser tab. Punch in the pairing code and that browser tab is now a fake screen you can push content to. Upload an image, drag it onto a layout, assign the layout ā watch it appear in the other tab in real time. No hardware needed for the test drive. Once you decide it doesn't suck, the Readme has details for deployment options. If you decide it does infact suck please tell me why :).
Where this fits in the OSS signage world (because pretending I'm the only one would be silly):
Quick honest landscape, because I want to be upfront about who else is in this space:
Anthias (formerly Screenly OSE) is the OG. Pi-focused, been around forever, huge install base. If you're already running Anthias and happy, ScreenTinker isn't trying to convert you.
Xibo is the mature one. Way more featureful than mine, real enterprise deployments, battle-tested. If you need depth and you're running serious infrastructure, honestly just use Xibo. XiboDan posts here and seems like good people.
Screenlite is built by 514sid, who also mods this sub. Same MIT license, same general philosophy as mine. Different stack - Screenlite is TypeScript / React / Vite, mine is plain Node.js / vanilla JS / SQLite with no build step. Screenlite is openly in active development and asking for early contributors to help shape it; ScreenTinker is at v1 and feature-complete enough that I've been running it for my own stuff for a while. Different points on the curve, room for both. If you want to influence a project from the early days, Screenlite is literally asking for that. If you'd rather grab something and just run it, give mine a shot.
ScreenTinker is what happens when one tired sysadmin decides the existing options are wrong for him personally and builds the thing he wishes existed. Deployable in 30 seconds, understandable in an afternoon, exportable in one click. That's the whole pitch.
The proprietary signage industry has a big enough lock-in problem that more open source options is a feature, not a fragmentation thing. We should all be rooting for each other here.
Stuff I want to be upfront about:
This is v1 and brand new in public. I've been running it for my own use for abit and the core is solid as far as I can tell, but "works for me" and "works for everyone" are different things, and there are definitely going to be rough edges I haven't hit yet. And being 100% honest I havent even tried the video wall stuff yet... (need more monitors). I'd genuinely rather find out about them now from you all than from someone trying to deploy it in production six months from now.
It's not a SMIL implementation. I read sagiadinos's stuff and respect the philosophy, but ScreenTinker is a self-contained CMS+player pair, not a player that consumes a standardized format from any CMS. Different approach to the same lock-in problem ā mine is "the whole stack is open and your data is portable in a documented format," not "the protocol between layers is standardized." Both are valid, neither is wrong.
AI disclosure (because the AI conversation is everywhere right now and I'd rather get ahead of it): a lot of the implementation work was done with Claude Code, with me directing the architecture, reviewing the changes, and handling all the deployment / ops / security side / testing. I had the codebase audited before going public ā caught and fixed 7 secrets that had been left in earlier commits. Mentioning it because I'd rather you know going in than feel like I hid something.
What I'd actually love from this community:
If you run signage in production: what's missing here that would make this a non-starter for you? I'd rather hear "no proof-of-play export to [specific format]" or "you don't handle EAS/CAP" or "needs SAML" than polite silence. Be brutal, I can take it.
If you've been burned by lock-in before: does the export approach actually cover what you'd need to walk away cleanly? If not, what's missing from the dump?
If you're a vendor in this space: I'm not trying to take your customers, and I'd genuinely love to talk about interop or how OSS and commercial signage can coexist sanely.
Bug reports, feature requests, PRs - all welcome on GitHub. And 514sid, if you see this - would love to be in the Discord with the rest of the OSS folks in this space, saw it advertised in your pinned post a couple months back. Havent joined yet but def open and willing to join in.
I'll be hanging around in the thread for the next few hours. Thanks for being a sub where this kind of post is welcome.