A clear brand system for AI and production infrastructure.
ScaleMule provides the production substrate for agent-built AI and API products through ScaleMule Cloud for product teams and MuleOS for infrastructure providers.
Primary message
Production infrastructure for agent-built AI and API productsProduction infrastructure for agent-built AI and API products
ScaleMule gives product teams and infrastructure providers the tenant-aware access, events, storage, audit trails, billing foundations, and operational workflows needed to move from generated product logic to customer-ready systems.
Positioning
What ScaleMule should mean
Launch faster
Package AI capability into customer-ready software without rebuilding auth, tenancy, workflows, storage, and audit foundations every time.
Control customer boundaries
Keep tenant isolation, scoped access, customer context, and audit trails visible as products move from prototype to paid use.
Prepare for commercialization
Build toward billing, metering, white-label packaging, partner delivery, and enterprise review with one reusable control model.
Messaging
Approved public language
Primary line
Production infrastructure for agent-built AI and API products
Use this as the homepage and campaign anchor. It is short, growth-oriented, and specific to ScaleMule.
Production infrastructure for agent-built AI and API products.
Production substrate for customer-ready AI and API products.
AI makes product logic cheap. Production boundaries become the scarce layer.
A reusable production control layer for AI and API products.
Hosted and provider paths built on one control model.
Voice
How ScaleMule should sound
Clear before clever
Explain what ScaleMule does in direct product language before using category language or campaign lines.
Technical, but customer-facing
Use real platform concepts like tenant-aware data, scoped access, audit trails, and event delivery without exposing internal implementation details.
Confident without unsupported proof
Avoid unsupported scale, assurance, latency, or customer claims. Enterprise buyers should feel precision, not exaggeration.
Do
- Use the full ScaleMule name in headlines and first references.
- Lead with customer outcomes before implementation details.
- Use product visuals to explain scoped access, tenant data, events, storage, and audit.
Avoid
- Do not make unsupported claims about assurance status, latency, customer count, or throughput.
- Do not describe ScaleMule as generic AI magic or a replacement for all cloud infrastructure.
- Do not stretch, recolor, rotate, or add extra effects to the logo mark.
Logo
Use the mark consistently
64px
48px
36px
28px
Keep clear space at least equal to the icon width. Use the mark on light, white, or quiet dark technical panels only.
Color
A focused enterprise palette
ScaleMule Blue
#2563eb
Primary CTAs, active states, core product highlights.
Signal Cyan
#06b6d4
Technical diagrams, event flows, secondary accents.
Growth Green
#10b981
Healthy states, successful workflows, readiness indicators.
Enterprise Slate
#0f172a
Headlines, dark product panels, high-contrast technical surfaces.
Cloud Surface
#f8fbff
Page backgrounds and quiet enterprise sections.
Muted Text
#64748b
Secondary copy, labels, captions, and support text.
Typography
Use real product language
Sora
Display headlines and confident product moments
Launch AI and API products faster.
Avenir Next
Body copy, navigation, CTAs, and customer-facing explanations
ScaleMule gives AI and API products the production foundation they need to keep growing.
JetBrains Mono
Code, events, request flows, logs, and technical labels
tenant_id = request.tenant && audit.logged = true
Product visuals
Make every mock explain a capability
Tenant request
Workspace: Acme AI / tenant: west-coast
Use product mocks that teach one platform concept at a time.
Prefer clear UI diagrams over raw application screenshots.
Use light enterprise surfaces by default and dark panels for code, terminal, and technical demos.
Every visual must survive mobile screenshots without clipped text or empty panels.
Launch illustrations
Launch illustration system
Cinematic illustrations for campaign moments — homepage hero, social, blog headers, investor decks, and emotional memorability. Use one cinematic image per page maximum. Product diagrams remain the primary way to explain capability.
City launch
Production infrastructure lifting off above the city.
Homepage hero campaign. Use when the goal is memorability and the headline is about carrying production workloads to market.
Cloud infrastructure
Hosted production infrastructure, above the clouds.
ScaleMule Cloud page. Pairs with hosted production, server, and product-builder narratives.
Provider horizon
Infrastructure becoming a customer-ready platform.
MuleOS page and provider campaigns. Pairs with commercialization, partner, and tenant-isolation themes.
Production mountain
Built for production scale.
Architecture page divider, reliability moments, and engineering blog headers.
Deep space campaign
Long-horizon launch story.
Investor decks, hero campaigns, and social launches. Reserve for moments that need scale and ambition.
Use launch illustrations for
Campaign moments — homepage hero, blog headers, investor decks, social launches.
One cinematic mule image per page maximum.
Pair with concise headlines; keep text overlays minimal and legible.
Use the navy/orange overlay treatment for enterprise polish.
Avoid
Do not stretch, recolor, rotate, or add filter effects to the artwork.
Do not place these behind dense paragraphs of text or technical diagrams.
Do not stack multiple cinematic illustrations on one page.
Do not replace product diagrams or technical mocks with cinematic art.