Building a media platform that stays private, dependable and yours.
Finetic already brings movies, television and music together on your own server. This is the human-readable journey from today’s public preview to the mature product we want it to become.
The source board, without a fake completion score.
These are GitHub roadmap entries, including five organising epics. They count decisions and work items—not effort, dates or percentage of the final product.
- Done
- 25 Implemented and verified
- In progress
- 17 Actively being worked on
- Todo
- 61 Planned or research
A complete foundation
The server, household experience and first public clients are already usable as one product.
You can install Finetic, add the media you own and use the features below today. Some areas will keep improving, but these are not concept mock-ups.Movies, television & music
- Movie and television libraries
- Artist-first music, albums, lyrics and queues
- Global search, collections, favourites and history
- Guided, read-only Jellyfin migration
Playback that explains itself
- Direct Play, remux, audio conversion and transcoding
- Resume, next episode, tracks, subtitles and quality controls
- Per-attempt playback evidence and recovery history
- Hardware acceleration controls and live sessions
A server you can operate
- Accounts, roles and library access
- Scoped guest sharing and guided remote access
- Health, analytics, jobs and library intelligence
- Backups, restore guidance and maintained updates
Clients you can use
- Responsive web application
- Windows x64 public-preview client
- Fire TV app on Amazon Appstore
- Android on supervised physical devices
Confidence on every press of Play
Current work is deliberately weighted toward reliability, safety and honest measurement.
Before racing onto more screens, Finetic needs to behave predictably with difficult files, interrupted networks, different devices and growing households.Playback confidence
- A representative cross-platform playback suite
- Faster cold starts and seeks for every conversion path
- Consistent audio and subtitle changes across clients
- Real-host GPU decode, tone-map and encode verification
Security & trust
- Complete and remediate the full security review
- Harden password-protected guest shares
- Remove sensitive values from media URLs and logs
- Sandbox media tools and add a container CVE release gate
Performance with evidence
- Validate completion, stopping and abandonment across clients
- Publish playback objectives and regression trends
- Build statistically meaningful benchmark distributions
- Continue the cross-client optimisation programme
Client stability
- Stabilise Android fallback playback and duplicate sessions
- Complete Xbox certification and the public Store release
- Create the supported Android beta release path
- Use one playback-conformance contract across clients
- Standardise Finetic identity and launcher artwork
A mature household product
The next horizon deepens the catalogue, household controls, recovery and supported-client experience.
This phase is about the details that make software dependable for years: correcting metadata safely, protecting families, recovering from failure and supporting more everyday devices.People & households
- Household profiles and a “Who’s watching?” flow
- Parental controls and content-rating rules
- Optional MFA or passkeys with account recovery
- Durable account-level playback preferences
Library craftsmanship
- Field-level metadata locks and visible provenance
- Alternate editions and media-version management
- Manual and smart collections, playlists and queues
- A guided Missing Media resolution workspace
Recovery & durability
- Ordered database migrations and integrity recovery
- Safer updates through interruption and restart failure
- Automated backup, restore and rollback drills
- Configurable background-work windows and budgets
More supported screens
- A supported Android beta
- Apple TV consumption client
- Samsung Tizen and LG webOS clients
- An installable iOS web app without an App Store dependency
Ambitious ideas, kept honest
Longer-term ideas remain visible without being presented as promised features or release dates.
Research exists so Finetic can prepare without distracting from today’s reliability work. Some ideas may change substantially—or never ship—if they do not earn their complexity.Shared experiences
- Synchronised Watch Together sessions with guests
- Explainable personal recommendations
- Per-user background artwork
- Real trailer discovery and playback
Open operations
- Administrator webhooks and external notifications
- Prometheus or OpenTelemetry operational metrics
- An internal supported-client API specification
- A formal native metadata-provider contract
Scale only when needed
- Multi-node playback and segment state
- DASH manifests over shared media fragments
- Per-session segment encryption
- DRM only for a concrete lawful requirement
Future living-room reach
- Roku after television contracts stabilise
- Additional clients only after shared behaviour is proven
- No platform announced as supported before release
- No dates invented to make the roadmap look certain
Direction without theatre.
A roadmap should help you judge the project—not pressure you with invented certainty.
The capability exists in a released or explicitly labelled testing build and has verification behind it.
Priorities can move when security, playback or real user evidence reveals a more important problem.
Roku, multi-node playback, DRM and similar ideas will not be sold as commitments before they have a justified need.
The server remains a free, unrestricted and non-expiring public preview. No paid server plan is currently offered.
Use what exists. Help shape what earns its place next.
Release notes show completed work; the roadmap shows direction. Useful feedback includes the device, workflow or problem you need—not just a vote for a feature name.
