Nixtla

Company
BABCO
Year
2026

Nixtla builds TimeGPT, a foundation model for time-series forecasting. Its dashboard is where developers create API keys, track usage and run their first forecast.

After the brand and website redesign, the dashboard looked like a different company. I audited every screen and redesigned the whole product on the same system as the site.

Nixtla usage dashboard
Role
Product designer, end to end
Scope
The whole dashboard: sign-in and profile setup, API keys, usage, billing, team, settings, playground, the component library, light and dark themes.
Platform
Web app, light and dark

Approach

  • 01

    Keep the flows

    Developers already knew where things were. Navigation stayed; hierarchy, type and states changed.

  • 02

    One system

    The site and the product share one set of tokens, so a new screen starts from the same parts.

  • 03

    Brand in the quiet moments

    Sign-in, empty states and loading carry the brand. Working screens stay plain.

Audit

Before and after

Before API keys
After API key management Personal and team keys are separate from the first visit.
Before Create key
After Create key Name, monthly limit and rate limit in one modal, with a reminder to save the key.
Screens

From first sign-in to first forecast

Sign in The site's illustration and code window carry over.
Pricing and billing Plan, usage and history on one page.
Playground Parameters on the left, the forecast on the right.
Team Members in a list, with roles and permissions inline.

Component library

Every control in the dashboard comes from one library. Each has its sizes and states defined, so a new screen is built from parts that already behave the same way.

  • 19component sets
  • 200variants
  • 10colours
  • 2themes, light and dark
01

Colour

Neutrals

Black #222121
Button hover #000000
Dark white #EAE9E6
Off white #F6F4F0
White #FFFFFF

Brand

Aubergine #433E6F
Deep water #8A94D4
Water #BFD1FF
Deep haze #A98DB6
Haze #D5BFDF
02

Type

Time GPT

PP Supply Mono. Buttons, labels, data. Uppercase, tracking −7%.

Usage

PP Neue Montreal. Titles, forms, body. 14 / 20 in controls.

03

Button

48 variants. Hover and tab through them
Large 48Medium 40Small 32Disabled
Primary
Neutral
Outline
Destructive
Text and tag
04

Input

24 variants
Data file
Choose file No file chosen
File variant.
05

Select

trigger, menu, item
Frequency
Daily
This is a select description.
06

Switch

16 variants
07

Radio group

12 variants
08

Toggle

30 variants. Press them

Default

Outline

09

Tabs and slider

10

Accordion

What counts as an API call?

Every request to a forecast or anomaly endpoint, whatever the size of the series.

Can I rotate a key?

Create a new key, switch your service to it, then revoke the old one.

Who can see team keys?

Admins see every key. Members see the keys they own.

11

Alert dialog and avatar

Revoke this key?

Services that use it will stop working right away.

DB DB DB
DBMK+3
12

Table and stats

patterns from the dashboard

Monthly usage

54%5,420 / 10,000 calls

Rate limit

200

Requests per minute

NameKey valueLast usedStatus
Production nixak-88a0f...2c9d 2 min ago Active
Staging nixak-41be7...9f02 3 days ago Active
Old pipeline nixak-07cd2...b1e8 94 days ago Unused
13

Library

components and patterns by group
Actions 5
  • Button
  • Toggle
  • Icon button
  • Copy button
  • Tag
Forms 11
  • Input
  • Select
  • Select menu
  • Radio
  • Switch
  • Slider
  • Checkbox
  • Text area
  • File input
  • Search
  • Field message
Navigation 8
  • Menubar
  • Navigation menu
  • Tabs
  • Sidebar
  • Workspace switcher
  • Page header
  • Breadcrumbs
  • Pagination
Feedback 8
  • Alert dialog
  • Accordion
  • Modal
  • Tooltip
  • Toast
  • Empty state
  • Loader
  • Progress bar
Data 10
  • Avatar
  • Table
  • Stat card
  • Bar chart
  • Line chart
  • Chart tooltip
  • Key row
  • Member card
  • Plan card
  • Code block
Foundations 6
  • Colour
  • Type
  • Grid
  • Spacing
  • Icons
  • Light and dark themes
Drag to move. Scroll or pinch to zoom.