Features

Why speed matters in a project tracker

Slow trackers cost minutes every day. How Starlex keeps boards, issues and whiteboards fast, and what to test in any tracker.

4 min read

Every click in a tracker happens dozens of times a day. A second of waiting on each adds up to real time and, worse, makes people avoid updating their issues.

Built lean

Starlex pairs a Go API with PostgreSQL and a SvelteKit interface. Pages load only the code they need: the maths renderer, the diagram editor and the whiteboard load when you open them, not before.

Live instead of polling

Boards and whiteboards receive changes over a single live stream. Cursor movements on whiteboards are relayed together many times a second without touching the database.

Fast when big

Large boards only draw the cards on screen and add the rest as you scroll. The database is indexed for the queries people actually run, and reviewed as features are added.

What to test in any tool

Open your biggest board, drag a card, open an issue and search. Do the same in Starlex. If the other tool feels slow with your real data, it will feel slower every day after.

  • Performance
© 2026 Starlex