How ARK360 looks and sounds.
Colour, type, voice, and terminology — everything needed to communicate ARK360 consistently. Designed for a dark, high-trust, specialist context.
Brand Identity
What ARK360 is — in one breath.
What we are
The governance layer between AI agents and mission-critical systems.
A specialist — not a general-purpose platform. Built for environments where AI must be verifiable, auditable and approved.
Who we serve
CIOs, CTOs, Heads of Digital/Security, GMs of Operations, Platform Architects.
In Australian government, construction, and complex enterprise — where AI adoption is blocked by the absence of governance, not the absence of use cases.
Our position
The specialist where Workato is the generalist.
Workato and Kong manage API traffic and workflows. ARK360 governs AI agent access — with the semantic tagging, compliance mapping and audit trails that regulated environments require.
Logo
Logo usage
Primary — teal tint on dark backgrounds
White — on very dark or image backgrounds
Dark — on white/light surfaces only
Do
- Use the teal-tinted version on dark backgrounds
- Maintain clear space equal to the height of the 'A' on all sides
- Scale proportionally — never stretch or distort
- Use on backgrounds with sufficient contrast
Don't
- Recolour the logo with non-brand colours
- Place the logo on low-contrast or busy backgrounds
- Add drop shadows, outlines or effects
- Use the logo smaller than 80px wide in digital contexts
Colour System
Tron-inspired. High-trust. Always dark.
The palette references the Tron aesthetic — a deep-space dark foundation with precisely placed teal/cyan energy. The site is always dark mode. Never render ARK360 on a white or light background.
Gateway Teal
Primary#26B9CB
hsl(190, 70%, 50%)
CTAs, links, active states, key highlights, gradient start
Signal Cyan
Accent#61D1BE
hsl(170, 55%, 60%)
Success states, secondary highlights, icon fills, gradient mid
Depth Blue
Tertiary#4D8FD4
hsl(210, 60%, 55%)
Third accent in gradients, step numbers, section accents
Deep Space
Background#080D11
hsl(210, 20%, 5%)
Page background. Always dark. Never lightened.
Surface
Card#0C1219
hsl(210, 20%, 7%)
Card and panel backgrounds. Elevated surface layer.
Boundary
Border#182230
hsl(210, 15%, 13%)
Dividers, card outlines, input borders. Always subtle.
Near White
Foreground#E7EEF0
hsl(190, 15%, 93%)
Primary text, headings, high-emphasis content.
Mist
Muted#7D8E94
hsl(200, 12%, 55%)
Body text, descriptions, secondary labels, captions.
Brand Gradient
Signal Cyan → Gateway Teal → Depth Blue
hsl(170,55%,60%) → hsl(190,70%,50%) → hsl(210,60%,55%)
Usage
- H1 gradient text — key words and headlines
- Animated with gradient-motion keyframe (4s, ease, infinite)
- Only applied to text using bg-clip-text + text-transparent
- Never used as a block background fill
Typography
Three typefaces. Each with a job.
Inter
system default
Primary body text, UI labels, navigation, form inputs
The governed layer between AI and your systems.
Geist Sans
--font-geist-sans
Display headings, hero text, section H2s
Mission-critical AI. Properly governed.
Geist Mono
--font-geist-mono
Step numbers, code labels, version strings, technical callouts
ISM-2084 · AU data residency · 01 / 03
Type Scale Reference
Voice & Tone
Confident. Direct. Specialist.
ARK360 speaks like the most knowledgeable person in the room — who also happens to understand the ICP's exact situation. Never preachy. Never corporate. Never vague.
Speak to the situation, not the feature.
Our audience has a specific problem: they can't get AI approved. Speak to that. Lead with insight, not product description.
Write this
“AI your security team will actually approve.”
Not this
“Governed MCP Connectors and Policy Presets for AI access.”
Confidence without arrogance.
We know this space. We've worked inside these systems. State things directly — no hedging, no corporate filler.
Write this
“Security says yes because they have evidence, not promises.”
Not this
“ARK360 can help organisations potentially improve their AI governance approach.”
Earned trust over claimed trust.
We never say 'trust us'. We describe the evidence, the audit trail, the proof. Trust is demonstrated, not declared.
Write this
“Every agent call logged. Every policy applied. Auditable on demand.”
Not this
“You can trust ARK360 to keep your data safe.”
Short sentences. Real rhythm.
Write the way people think in high-stakes meetings. Short. Direct. No meandering. Sublines in three punchy clauses beat one long sentence.
Write this
“Your CISO gets evidence. Your teams get access. Leadership gets answers.”
Not this
“ARK360 provides comprehensive evidence for security teams while enabling productive AI usage and complete leadership visibility.”
Terminology
Approved product terms.
Consistent terminology builds category ownership. These terms are always written exactly as shown — capitalisation matters.
| Term | Usage rule |
|---|---|
| MCP Connectors | The governed API wrappers ARK360 generates. Always capitalised. Never 'MCP connectors' (lowercase). |
| Policy Presets | Pre-built governance rule sets. Always capitalised. Never 'policies' or 'presets' alone in product context. |
| Governed MCP | Our category descriptor. Use to contrast with 'basic MCP' or 'raw MCP'. Never 'managed' or 'controlled'. |
| Governed MCP Gateway | The product category ARK360 occupies. Use in full on first reference. 'Gateway' acceptable thereafter. |
| Mission-critical | Always hyphenated. Describes the environment we're built for — not a marketing claim. Use sparingly and accurately. |
| Operations Dashboard | The monitoring interface. Always capitalised as a proper noun. |
| Audit trail | Lowercase. Specific and technical — not 'audit log' or 'audit record'. |
| Data residency | Lowercase noun. Not 'data locality' or 'data location'. Pair with 'data sovereignty' to distinguish the two. |
| AU-only | Hyphenated when used as a modifier: 'AU-only routing'. 'Australian' in prose. |
Words to avoid
UI Patterns
Recurring interface elements.
Eyebrow badges
Used above H1s. Always small, always all-caps, always teal. The pulsing dot variant signals an active/live section. Flat dot for static labels.
Buttons
Primary: filled teal, semibold, always with arrow icon. Secondary: border-only, matches background. Inline: text-only link for in-content navigation. CTAs always go to /about#contact unless routing to a specific page.
Cards
Standard card
Feature title
Description text in muted foreground.
Highlighted card (primary)
ARK360 Governed MCP
Used for the preferred/recommended option in comparisons.
Standard: border-border bg-card with rounded-xl. Highlighted: border-primary/30 bg-primary/5 ring-1 ring-primary/10. Always 8px radius. Never rounded-2xl or square.
Section dividers & glows
↑ Section top divider
↑ Subtle divider (between items)
↑ Background glow orb
Top dividers use via-primary/20. Subtle dividers use via-border. Glows are absolutely positioned, pointer-events-none, using blur-[80px] to blur-[140px]. Never use a hard solid divider line.
Need brand assets?
Logo files, SVG exports, and other brand assets are available on request. Contact the team directly.
Request assets