Step 13 of 15 · Speed at scale · topic 2 of 4
How it stays fast
Nine things the platform does for you
Dashboards from RedisEach person's and each team's dashboard figures are worked out in the background, off-peak, and kept in Redis. Opening a dashboard reads a prepared answer — it never counts millions of rows while the user waits.
Work lists from RedisPages of every work list are kept in Redis for a time you set per company, so the second and every later look is served from memory. Lists can also be switched to live.
Menus from RedisEach user's menu is kept in Redis and refreshed only when an administrator changes menus.
Screens from memoryScreen designs are held in the server's memory and refreshed the moment a designer saves.
Saves that return at onceA save is checked, stored and acknowledged straight away; writing into the reporting tables happens behind the scenes.
Page by pageLarge lists come one page at a time, so a huge result never has to load at once.
Heavy queries flaggedLists whose queries would be expensive are flagged when they are configured, before users meet them.
Slow calls watchedSlow database queries and slow outside calls are logged, so they can be fixed before they spread.
More servers when neededAdd servers behind a load balancer; they share one Redis for data, sessions and real-time updates.
Build your first app free
Up to 10 users. 30 days to build, then 30 days live after go-live.
Updated 30 September 2026