ApertureDB Cloud

Selected project · ApertureDB Cloud

A cloud consolefor multimodal AI.

ApertureDB Cloud is where engineers create a database, pick ready-made AI workflows and keep an eye on usage and billing. I designed the console end to end: sign-up, the dashboard, the workflow hub and details, instances and billing, on one UI kit.

Your data
Role
Product designer · UX, UI, UI kit
Timeline
2024 – 2025
Scope
Sign-up, dashboard, workflows, instances, billing
Platform
Web app, desktop first
0setup steps from “what data?” to a running database
0main sections in a sidebar that folds to icons
0views of every workflow: video, details, reviews, empty
0billing states, including months with no data
0interaction states for every control

Where it started

From “request a trial” to self-serve

The old site asked for an e-mail and promised a call. Now an engineer signs up with e-mail or Google, sees the product promise beside the form, and lands on a dashboard with a database already running.

The 2022 trial request page
Before · 2022
ApertureDB Cloud sign-up
After · sign-up today

Dashboard

One screen that answers “what’s going on?”

Usage, money, new workflows and the next step, in the order a returning engineer looks for them.

Sidebar
Dashboard, sidebar expandedDashboard, sidebar folded to icons

Workflows

From catalogue to running in one place

The Workflows Hub groups what you run, what is new and everything else, with filters by data type. Each workflow gets a page with a short video, real documentation and reviews from other teams.

Workflows Hub
Workflows Hub
Workflow details: Video how-to

Billing

Spending you can read

Month by month, then tier by tier, then instance by instance. Coupons show where they were applied, and an empty month says so instead of showing zeros. (First release, before the console moved to the sidebar layout.)

Billing: Month overview

UI kit

Every control has four states

Default, hover, pressed and disabled for navigation, buttons, icon buttons, links and chips, built on named tokens so the console and the website stay one family.

Interaction states

Default, hover, pressed and disabled states for navigation, buttons and links

Core tokens

  • AD Blue Primary#172F94
  • AD Dark Blue Primary#030933
  • AD Violet (actions)#786CF8
  • AD Text#101720
  • AD Medium Gray#9FA2AE
  • AD Light Gray#EDEDED
  • App background#F3F4F7

Type

AaAa

Poppins for headings and numbers, Roboto for everything you read

Key decisions

  1. 01The dashboard changes with the user

    New users get a banner and a checklist; returning users get the space back.

  2. 02Numbers always lead somewhere

    Every stat card has a shortcut to the page behind it.

  3. 03Workflows are products

    Each one has a video, documentation and reviews, like an app store page.

  4. 04Empty is a state, not an error

    Billing and reviews say what is missing and what comes next.

  5. 05One main action

    “Create Instance” is the only filled button in the top bar.

  6. 06One kit for site and console

    The same tokens, type and violet actions as the marketing site.

Outcome

From a sales form to a product people run on their own

Self-serve sign-up, a dashboard that grows with the user, a workflow hub with real product pages, readable billing and one UI kit shared with the website.

See the brand and website projectAll names, numbers and texts in the screens are design placeholders.