Prediction Stack docs
v1.0.0
Live app Get help
● Set up · Your name and colours

Rebranding
make it yours.

Most branding is a setting in the admin. Icons, the page themes and the page titles are files you replace or edit.

01From the admin (no code)

SettingWhere it shows
Brand → Product name, taglineHeader of the landing page, Scanner and Terminal. Empty keeps the built-in name.
Brand → Accent colourReplaces the theme accent (#rgb or #rrggbb).
Brand → LogoAn http(s) image URL or a data:image URL.
Brand → Support email, websiteFooter.
Legal → Terms, privacy, disclaimerFooter links and text.
Alert bot → username, channel linkFooter link to Telegram.

Save, then commit and deploy config/public.json (how).

02Files you replace

FileWhat it is
favicon.pngBrowser tab icon of the landing page.
apple-touch-icon.pngHome-screen icon on phones (landing page).
brand/logo.pngHeader mark on the landing page.
scanner/public/admin.html, terminal/public/admin.html, bot/public/index.htmlPublic operator notices. They explain that the admin runs on the operator's own computer, show a dated screenshot of the admin and link to the docs; they never link to 127.0.0.1. Point the links at your own documentation if you move it.
<title> and meta tags in index.html, scanner/public/index.html, terminal/public/index.html, bot/public/index.htmlThe text in the browser tab and in link previews.

Keep the same file names and sizes, or update the references in the HTML files.

03Themes and stylesheets

Each page's stylesheet is built from a shared base plus its own theme, so the Scanner and the Terminal do not look alike:

SourceUsed by
design-system/mikodes-pm.cssBase for all pages.
design-system/theme-scanner.cssScanner.
design-system/theme-terminal.cssTerminal and the bot page.

After editing, rebuild the public/assets/app.css files:

sh design-system/build.sh

Do not edit public/assets/app.css directly; the next build overwrites it. The landing page keeps its styles inside index.html.

04Wording rules to keep

The pages say spread, difference in pricing and historical data, describe the product as read-only market data and analytics, and never present a spread as a return or promise earnings. Keep that when you edit text, write your disclaimer or promote your site. Do not use Kalshi's or Polymarket's logos or wordmarks; the pages ship without them.