Strategy
- 1.1Brand Conviction
- 1.2Brand Promise
- 1.3Experience Principles
- 1.4Brand Character
- 1.5Brand House
Our Brand Conviction defines the deeper purpose driving the brand — the belief or motivation that fuels everything it stands for.
The standard for database development
Our Brand Promise outlines the core commitment the brand makes to its customers and what value it consistently delivers.
The unified platform for governing how teams access and change any database.
Our Experience Principles are guiding feelings and behaviors that shape every brand interaction and expression. They’re informed by research that shows the current climate of the industry, and how we want to implement change.
Dependable
We operate as a trusted standard: transparent, governed, and built for environments where correctness is non-negotiable. With Bytebase, you have complete trust in how the system behaves.
• System of record • Safety-first • Predictable • Auditable • Governed by design • Resilient • Open-source
Connected
We deliver end-to-end database change governance in a single, unified workflow. Everything in our brand feels deeply connected.
• Unified • End-to-end • No silos • Workspace • Collaborative • Organized • Building blocks
Innovative
We don’t shout — we lead. Confident and expert, Bytebase sets the modern standard for a new category by showing a better way forward.
• Category-defining • Conviction • Expert-led • Modern standard • Clarity over disruption • Built by practitioners
Intuitive
We remove complexity for devs with frictionless, automated workflows. The experience is secure but approachable, built to empower teams.
• Developer-friendly • Thoughtful design • Calm, minimal • Accessible technicality • Modern • UX with intention
Brand character defines the personality and role the brand plays for its users. It guides how the brand communicates, behaves, and supports its audience across every touchpoint.
The Database Steward
01
The Database Steward maintains the fabric that binds modern database work: access, change, context, control.
02
Like a guardian of an invisible but essential layer, it unifies what was once scattered — connecting teams, databases and environments into a single, governed plane.
03
The Database Steward is modern, technical and confident, defining the standard not by force, but by clarity. It governs without slowing; protects without constraining; orchestrates without overshadowing.
04
A pragmatic visionary who sees the database estate as a living system and knows exactly how to keep it organized and secure.
Our Brand House brings together all our strategic components into one cohesive framework and crystallises our brand’s unique positioning.
Positioning
A category claim
The standard for database development
Value Proposition
What we enable
The unified platform for governing how teams access and change any database.
Experience Principles
Big guided behaviours
(often visual/metaphorical)
Dependable
Connected
Innovative
Intuitive
Tone of Voice
Personality traits in language
Deeply pragmatic
Empathetic
An expert
Crystal clear
Verbal Identity
- 2.1Voice Characteristics
- 2.2Linguistic Techniques
- 2.3Feature Messaging
- 2.4Style & Mechanics
Our tone of voice characteristics align with our conviction, promise and experience principles. We should keep these front of mind when creating any written content.
Deeply pragmatic
Our voice is practical, grounded, and solutions-focused. We’re not a “big-future-thinking” or visionary brand. Communication should lean toward real problems solved today, not abstract future-state narratives.
Empathetic
We communicate in a way that brings every part of DevSecOps together, speaking clearly to developers, DBAs, platform teams and security leaders to demonstrate we understand their pains. We meet each audience where they are.
An expert
We speak with the quiet confidence of experts: practitioners who know the terrain and lead by example. Confident statements, not speculation. Teaching through clarity, not provocation. The tone of people who have done this before.
Crystal clear
Even though Bytebase is technical, we value simplicity and intuitive UX. Our voice should feel intelligent but must be clear and easy to understand. Lean into clear explanations, but avoid being too casual or friendly.
Isocolon
Isocolon is a rhetorical device that uses balanced phrasing — lines or clauses that match in length, rhythm, and grammatical form.
This structure creates clarity and emphasis by presenting ideas in controlled, parallel units. The balance reflects system logic: inputs and outputs, actions and outcomes, rules and enforcement.
Many Bytebase messages use isocolon to mirror the predictable, structured nature of database workflows. These short pairings or trios help communicate governance and control without unnecessary explanation.
How we use it
Secure access. Safe changes.
Examples
Fast changes. Fully governed.
Policy defined. Enforcement automatic.
Review required. Deployment approved.
Declarative system statements
Declarative system statements describe what the system **does or enforces**, rather than what the product promises or aspires to do.
Instead of persuasive language or feature claims, these statements present the system as an active authority. The message focuses on **rules, enforcement, and outcomes** rather than benefits alone.
This reinforces Bytebase as infrastructure — a system that governs database changes and applies policy consistently across environments.
How we use it
Guardrails enforced. Policies applied.
Examples
Access restricted. Activity logged.
Reviews required. Changes tracked.
Policies defined. Enforcement automatic.
Verb-led workflow chains
Verb-led workflow chains describe processes through short sequences of actions. Each verb represents a step in a controlled workflow.
These sequences reflect the operational reality of database change management: changes move through defined stages before deployment. The language mirrors that structure.
Using concise verbs makes workflows immediately understandable and reinforces Bytebase’s role in orchestrating the process.
How we use it
Request. Review. Approve. Deploy.
Examples
Plan. Apply. Audit.
Propose. Validate. Execute.
Commit. Review. Release.
Parallel noun phrases
Parallel noun phrases reinforce consistency across environments, roles, or systems by repeating the same grammatical structure.
This pattern helps communicate scale and coverage: one system applied across many teams, databases, or environments.
The repetition emphasizes that governance and workflows remain consistent everywhere Bytebase operates.
How we use it
One workspace. Every role.
Examples
One workflow. Every database.
One policy. Every environment.
One system. Every team.
Features
Access
Change
Collaboration
Governance
Examples
Secure access. Governed roles. One shared workspace.
Governed access for every role, from developers to DBAs, in one unified workspace.
Request. Review. Approve. Deploy.
A standard workflow for requesting, reviewing, and safely deploying database changes.
One space. Every role.
Clear handoffs between Dev, DBA, Sec, and Platform teams — all in one governed space.
Guardrails enforced. Policies applied. Audits built in.
Built-in guardrails, audit trails, and policy enforcement across all environments.
These rules lay the foundations for our brand voice and should be maintained at all times to ensure consistency and professionalism.
Lead with the system
Example: Database changes, fully governed.
Why: Start with the system capability, not the context. Readers should immediately understand what Bytebase enables.
Keep sentences controlled
Example: Fast changes. Full audit history.
Why: Short, structured sentences reflect the controlled workflows Bytebase enforces.
Use declarative statements
Example: Policies enforced. Changes tracked.
Why: Bytebase language describes what the system does — not what it hopes to achieve.
Reflect real workflows
Example: Request. Review. Approve. Deploy.
Why: Language should mirror the operational steps teams follow when managing database changes.
Ground claims in mechanism
Example: Schema changes versioned and reviewed before deployment.
Why: Avoid vague benefits. Explain the system behaviour that produces the outcome.
Use parallel structure
Example: One workspace. Every database.
Why: Parallel phrasing reinforces the consistency and coverage of the system.
Over-explain
Example: Bytebase is a comprehensive platform designed to streamline database change management across complex infrastructure environments.
Why: Say what the system does first. Add detail only where necessary.
Stack features in one sentence
Example: Secure, scalable, flexible database governance with CI/CD integrations, approval workflows, audit logging, and policy enforcement.
Why: Focus on one clear idea at a time.
Use marketing adjectives without explanation
Example: Powerful database governance.
Why: Words like powerful or seamless mean nothing without describing the mechanism.
Use metaphor or analogy
Example: The engine powering database DevOps.
Why: Bytebase is infrastructure. Describe the system directly.
Write long, abstract sentences
Example: By enabling teams to orchestrate database changes through structured automation and flexible configuration frameworks…
Why: Break ideas into clear, controlled statements.
Hedge or soften the message
Example: This can help teams manage database changes more effectively.
Why: Be bold. No need to soften or second-guess.
Logo
- 3.1Overview
- 3.2Colour Applications
- 3.3Clear Space
- 3.4Social Avatar
- 3.5Usage
Our logo is designed to work clearly across both light and dark environments.
On light backgrounds, our logo appears in its night color to maintain strong contrast and legibility. On dark backgrounds, our logo switches to its light version to ensure it remains visible and consistent.
Both the full logo and the icon follow this rule, allowing the mark to adapt to different surfaces while preserving clarity, balance, and brand recognition.
Night logo
Light background
Night Icon
Light background
Light logo
Night background
Light Icon
Night background
Favicon
Workflow diagram
Cards
Signage
Brand Device
- 4.1Overview
- 4.2Shape Meaning
- 4.3Access Control
- 4.4Deploy/Change
- 4.5Governance
- 4.6Integration
Logo
Motion
Icons
Logo
Motion
Icons
Logo
Motion
Icons
Logo
Motion
Icons
Color Palette
- 5.1Primary Color Palette
- 5.2Secondary Color Palette
- 5.3Tertiary Color Palette
- 5.4Abstract Palettes
- 5.5Two-tone Patterns
Light
HEX: #FFFFFF
RGB: 255 255 255
Night
HEX: #0B110F
RGB: 11 17 15
Night/75
HEX: #111819
RGB: 17 24 25
Night/50
HEX: #1F2828
RGB: 31 40 40
Night/25
HEX: #2D3535
RGB: 45 53 53
Apple
HEX: #3B7F0D
RGB: 59 127 13
Forest
HEX: #55B216
RGB: 85 178 22
Lime
HEX: #B4F34D
RGB: 180 243 77
Ocean
HEX: #1C49BE
RGB: 28 73 190
Cobalt
HEX: #2B66FF
RGB: 43 102 255
Sky
HEX: #4FAAFF
RGB: 79 170 255
Grape
HEX: #681B92
RGB: 104 27 146
Violet
HEX: #AD2DF1
RGB: 173 45 241
Blackcurrant
HEX: #C973FF
RGB: 201 115 255
Copper
HEX: #B95D1F
RGB: 185 93 31
Amber
HEX: #EA6B35
RGB: 234 107 53
Orange
HEX: #FF9F5B
RGB: 255 159 91
Slate/100
HEX: #CFD5E0
RGB: 207 213 224
Slate/80
HEX: #DBE0EA
RGB: 219 224 234
Slate/60
HEX: #E3E8F3
RGB: 227 232 243
Slate/40
HEX: #E9EEF9
RGB: 233 238 249
Slate/20
HEX: #F5F6FF
RGB: 245 246 255
Typography
- 6.1Primary Typeface
- 6.2Secondary Typeface
- 6.3Google Font Alternatives
Our primary typeface is APK Protocol. It is a modern sans-serif designed for clarity, precision, and strong digital readability.
Its clean geometry and balanced proportions reflect the structured and technical nature of our platform while maintaining a confident and contemporary tone.
We use our primary typeface for headings, body copy, interface labels, and key product moments to establish clear hierarchy and ensure our communication remains consistent, direct, and recognizable across our brand.
APK
Protocol
Regular
Medium
Semi-Bold
AaBbCc
0123
Our secondary typeface is Era Mono. It is a monospaced typeface that conveys precision, structure, and technical clarity, reflecting the engineering focused nature of our platform.
Its consistent character spacing and highly legible forms make it especially effective for smaller text, code references, and supporting information.
We use Era Mono, technical annotations, and system related content where clarity and readability are essential.
a b c d e f g h i j k
l m n o p q r s t u v
w x y z
0 1 2 3 4 5 6 7 8 9
Regular Medium
When our primary and secondary typefaces aren't available, we can use Google Fonts alternatives for use across material such as Google Slides, Google Docs, or shared environments. These typefaces offer a close visual match, preserving tone and structure while ensuring full accessibility across platforms.
Primary Typeface
Google Font Alternative
Secondary Typeface
Google Font Alternative
Iconography
- 7.1Icon Grid
- 7.2Icon Library
Our icons are constructed using the same geometric foundations as our abstract shape system. Each icon is built from simplified versions of our core shapes, ensuring visual consistency across our brand.
By aligning these forms to a structured grid, our iconography remains clear, balanced, and instantly recognizable while staying connected to our broader visual language.
We have created a number of icons for use across our website and other marketing material, all following the same style and aesthetic to create a consistent suite of icons that are unique to Bytebase.