Skip to content

ARK360 Brand Guide & UI Kit

Brand Guide & UI Kit

The operating system for build-to-rent.

The standards that keep ARK360 consistent across every surface, from a proposal to a production console. One mark, one palette, one voice.

ARK360
VERSION 1.0UPDATED JUN 2026OWNER ARK360
01 — Foundation

What ARK360 stands for

Our purpose is simple: let people spend their effort on what only people can do. We build intelligent, governed systems for high-stakes, regulated property and construction work, so the teams who run it can focus on the judgment only they can bring.

Mission

Amplify human excellence, so that what we build leaves the world better than we found it.

Positioning

ARK360 is built around a single product, BTR OS, for a single sector, Australian build-to-rent. We hold governance, audit and compliance from the first line of code, and we ship into live operations.

Brand pillars

01

Property is the domain

We specialise in property. We know the workflows, the systems and the compliance because we have shipped inside them.

02

Built for the people inside

The resident, the worker, the occupant is who the software is for, not the org chart.

03

Governed and compliant by design

Access control, audit trails and compliance built in from the start, never bolted on.

04

Less friction, more done

We remove operational friction so teams focus on the work that matters.

05

Production over prototype

We ship into live property operations and stand behind what runs.

06

Built to endure

Made to hold up in regulated property and government environments for the long term.

03 — Colour

Palette

ARK Navy carries weight and trust; ARK Teal is the signal of intelligence and the single accent. Used sparingly, the teal does the work. Tap any swatch to copy its hex.

Brand

Navy & ink scale

Neutrals

Functional

Accessibility ruleSolid teal call-to-action buttons use Teal Ink (#0F7A8A) with white text to clear WCAG AA. Reserve bright ARK Teal for decorative accents. For teal text or links on a light background, use Teal Ink.
04 — Typography

Type system

Inter is the single brand typeface. Weight does the expressive work: heavy and tight for display, regular for reading. JetBrains Mono labels anything technical, the system readout voice carried from the product surface.

Primary
Inter

Display, headings, body, UI. Weights 300 to 800.

Utility
JetBrains Mono

Labels, tokens, code, data and timestamps.

Scale

Intelligent systems
Display · Inter 800 · 46px
Section heading
H1 · Inter 700 · 30px
Subsection heading
H2 · Inter 600 · 22px
Body copy carries the detail at a comfortable reading size.
Body · Inter 400 · 16px
Secondary and caption text for metadata.
Small · Inter 400 · 13px
SYS.LABEL — 042
Label · JetBrains Mono 500 · 12px · uppercase

Weights

AaLight 300AaRegular 400AaMedium 500AaSemibold 600AaBold 700AaExtrabold 800
05 — Motif & Icons

The hexagon system

The six-segment hexagon is the brand's structural device. Use it as a section marker, a list anchor, or a quiet background watermark. Icons share its language: 1.5px strokes, rounded joins, geometric and even.

Solid · primary

Teal on navy · accent

White on navy · reverse

Tint · watermark

Even stroke weight, rounded terminals, 24px grid. Lucide is the recommended base set.

06 — Voice & Tone

How ARK360 sounds

An honest practitioner. Plain verbs, sentence case, no filler. We earn trust by being specific, not by being clever or grand. Claims are evidenced, and we never use an em dash.

Do
  • +Lead with what was built and what it does.
  • +Use active voice: "Save changes", not "Submit".
  • +Name things by what people control and recognise.
  • +Keep one job per sentence.
  • +Quantify outcomes you can stand behind.
Don't
  • ×Reach for "leverage", "synergy" or "best-in-class".
  • ×Hide the system behind jargon the reader did not ask for.
  • ×Apologise in errors or be vague about what happened.
  • ×Inflate. If it is a proof of concept, call it one.
  • ×Use em dashes. Use a comma, a colon, or a full stop.
07 — Tokens

Design tokens

The numeric system every component is built from. Spacing runs on a 4px base, so layouts stay on a predictable rhythm.

Spacing

--s-1tight insets, icon gaps4px
--s-2chip padding8px
--s-4control padding, card gaps16px
--s-5card padding24px
--s-7block separation48px
--s-9section rhythm96px

Radius

--r-xs4px
--r-sm8px
--r-md10px
--r-lg14px

Elevation

--e-1resting cards
--e-2hover, dropdowns
--e-3modals, popovers
08 — UI Components

Component library

Live components built from the tokens above. These are the building blocks for ARK360 product interfaces and client consoles.

Buttons
Form fields
Badges & status
NeutralAgenticOperationalDegradedOfflinev1.0.NET ASPIREAZURE AI FOUNDRY
Alerts
Heads upA new agent version is available. Review the changelog before promoting to production.
DeployedTask Hazard Review agent is live in the production workflow.
Action neededStandard deployment may route outside Australia. Switch to provisioned throughput for PROTECTED workloads.
Connection failedThe access gateway did not respond. Check the device network and retry.
Cards

Product Engineering

Problem to shipped product, owned end to end.

LIFECYCLEEND-TO-END

Governed AI Adoption

Security, onboarding and architecture for the enterprise.

FRAMEWORKSECURE
1 wk
POC to production
Data table
ServiceEnvironmentStatusLast deploy
BTR OSProductionOperational17 Jun, 09:14
Access GatewayProductionDegraded17 Jun, 08:02
THR AgentStagingBuilding16 Jun, 21:40
Navigation
Console/BTR OS/Access points
Code & terminal (signature)
ark360@main ~ ./deploy_agent
1import { EnterpriseAgent } from '@ark360/core';
2const agent = new EnterpriseAgent({
3  mode: 'production',
4  compliance: true,
5});
6await agent.deploy();
09 — Patterns

Putting it together

The system on its two home surfaces. Light for documents and reading, navy for product chrome and presentation.

Dashboard

Resident access

42 active credentials across 3 buildings.

All systems operational
SYS.STATUS
Systems nominal
LiveUPTIME 99.98%
ARK360 Brand Guide & UI Kit · v1.0ark360.com.au