BYOS

Buy a TRMNL device, then point it at your own server.

First, purchase a TRMNL from our home page. Then choose a BYOS implementation for your stack. Our reference implementation is Terminus (Hanami) and we recommended you get started there but you can also choose from other languages/frameworks as well.

Why BYOS?

TRMNL intends to ensure that every device is un-brickable and can run with zero external dependencies.

Implementations

We support multiple implementations developed by us and the community at large. The goal isn't for BYOS to match parity with our hosted solution but to provide enough of a pleasant solution for your own customized experience. There are trade offs either way but we've got you covered for whatever path you wish to travel.

Legend

Use this legend to understand the matrix of features below.

• 🟢 Supported.

• 🟡 Partially supported.

• 🔴 Not supported or not implemented.

• ⚫️ Archived with minimal maintenance support.

• ⚪️ Unknown.

Matrix

Below is a list of all implementations in various languages/frameworks you can use to self-host and manage your devices with:

Implementation	Dashboard	Auto-Provisioning	Devices	JSON Data API	Image Previews	Playlists	Plugins	Recipes	Docker	Maintained	Semantic Versioning
TRMNL Terminus (Ruby + Hanami)	🟢	🟢	🟢	🟢	🟡	🔴	🔴	🔴	🟢	🟢	🟢
TRMNL (Ruby + Sinatra)	🟡	🔴	🟡	🟢	🔴	🔴	🔴	🔴	🟢	⚫️	🟢
TRMNL (Elixer + Phoenix)	🔴	🔴	🟢	🟢	🟢	🟢	🔴	🔴	🔴	🔴	⚪️
Community (Python + Django)	🔴	🔴	🔴	🟡	🔴	🔴	🔴	🔴	🔴	🔴	⚪️
Community (PHP + Laravel)	🟢	🟢	🟢	🟢	🟢	🟢	🟢	🔴	🟢	🟢	🔴
Community (Next.js)	🟢	🟢	🟢	🟢	🟢	🔴	🔴	🟢	🔴	🟢	⚪️

Here's a more detailed breakdown of each feature:

• Dashboard: Provides a high level overview of information.

• Auto-Provisioning: Means that a device can be automatically provisioned once added to your network. This includes the automatic provisioning of new and existing devices.

• Devices: Provides device management in terms of updating each device, viewing current image, viewing logs, and more.

• JSON Data API: Provides full API support using a JSON Data API for device management, image generation, logging, etc.

• Image Previews: Provides a UI for viewing generated images for devices, plugins, recipes, etc.

• Playlists: Supports hosted playlist feature.

• Plugins: Supports hosted plugins feature.

• Recipes: Supports hosted recipes feature.

• Docker: Supports Docker for both local development and production deployment.

• Maintained: Project is maintained and kept up-to-date on a weekly basis.

• Semantic Versioning: Supports strict semantic versioning.

API

At a minimum, the following API endpoints should be supported for all BYOS implementations:

Display

curl "http://byos.local/api/display" \
     -H 'ID: <redacted>' \
     -H 'Access-Token: <redacted>' \
     -H 'Accept: application/json' \
     -H 'Content-Type: application/json'

Images

curl -X "POST" "http://byos.local/api/images" \
    -H 'ID: <redacted>' \
    -H 'Access-Token: <redacted>' \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json' \
    -d $'{
 "image": {
   "content": "<p>Demo</p>"
   "file_name": "demo"
 }
}'

Logs

curl "http://byos.local/api/log" \
     -H 'ID: <redacted>' \
     -H 'Access-Token: <redacted>' \
     -H 'Accept: application/json' \
     -H 'Content-Type: application/json'

Setup

curl "https://byos.local/api/setup/" \
    -H 'ID: <redacted>' \
    -H 'Access-Token: <redacted>' \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json'

💡 For a detailed breakdown of all API endpoints and what they can do, please refer to the Terminus API Documentation.