Official name
Amevia
Brand Book · v1.2.0
Amevia
Your website’s AI workforce.Engage visitors, answer questions, automate tasks and take action 24/7.
Brand identity · Version 1.2.0 · Jul 2026
A product by
Brand overview
Amevia is an AI agent platform that transforms websites into intelligent, action-driven experiences. It engages visitors, answers questions, recommends products and services, captures leads, and automates workflows in real time.
Primary domain
getamevia.com
Parent company
Dioartis Grup SRL
Platform
AI Website Agent Platform
Tagline
Your website’s AI workforce.
Core promise
Engage visitors, answer questions, automate tasks and take action 24/7.
What Amevia is
Amevia combines conversational intelligence, product discovery, lead generation and website automation in one platform.
Capabilities
- Conversational AI
- Product and service recommendations
- Lead capture and qualification
- Customer support assistance
- Workflow and action execution
- Multilingual interactions
Integrations
- Websites and CMS platforms
- E-commerce systems
- CRM platforms
- Email and support tools
- Booking and reservation systems
- APIs and custom workflows
How Amevia works
Amevia connects website visitors with the information, products and actions they need.
- Visitor
- Website
- Amevia Agent
- Outcomes
- Answers
- Recommendations
- Leads
- Actions
Connected destinations
- CRM
- Commerce
- Bookings
- APIs
Design principles
The Amevia experience should always feel useful, clear and trustworthy.
Intelligent
Every interaction should feel relevant and context-aware.
Helpful
Guide visitors toward the right answer or next step.
Fast
Responses and actions should feel immediate.
Trustworthy
Be transparent, secure and privacy-conscious.
Invisible
Automation should reduce friction, not create it.
Platform summary
Deployment
Designed for quick website integration
Languages
Multilingual by design
Availability
Built for 24/7 assistance
Compatibility
Works across different website platforms
Extensibility
Connects through integrations and APIs
Strategy
Purpose-built to make every website conversation useful — guiding visitors with clarity and connecting them to meaningful actions.
Purpose
To make every website conversation useful — helping visitors find answers, discover what matters, and take meaningful next steps.
Mission
Build intelligent website agents that understand context, guide visitors with clarity, and connect conversations to real actions across any website.
Vision
A world where every website offers helpful, human-centered guidance — without adding complexity for the businesses that run them.
Deep dive
Explore the full brand strategy
Review Amevia’s positioning, audiences, values, messaging, differentiation and long-term direction.
Estimated reading time: 10–12 minSource format: Markdown
Logo
Logo system
Built for every context
The Amevia logo system includes flexible lockups for digital products, websites, presentations, partnerships and print.
Approved brand assets- 10 approved variants
- 4 icon variants
- SVG · PNG
- Version 1.0
- Updated July 2026
- 3.7 MB
Download logo packageBrowse assets
Includes all approved logo, icon, monochrome, favicon and app-icon assets.
Primary horizontal logo
RecommendedThe preferred Amevia lockup for website headers, presentations, product pages and most general brand applications.
Logo variants
Browse approved lockups by category, tone, or filename.
Primary
PrimaryHorizontal · Light
Primary
PrimaryHorizontal · Dark
Secondary
SecondaryStacked · Light
Secondary
SecondaryStacked · Dark
Secondary
SecondaryWordmark only
Compact
CompactSymbol only
Monochrome
MonochromeMonochrome black
Monochrome
MonochromeMonochrome white
With descriptor
With descriptorHorizontal with descriptor
With descriptor
With descriptorStacked with descriptor
Clear space
The minimum clear space around the Amevia logo is one quarter of the symbol width on all sides.
No text, UI chrome, or other graphics may enter the exclusion zone. The unit ¼w equals one quarter of the symbol width.
Correct — clear space preserved
Avoid — tight placement enters the exclusion zone
Minimum size
Digital minimums follow the official logo guidelines. Print values below are recommended working sizes until print specs are formally published.
Digital
- Icon only24 × 24 pxFavicon may use 16 × 16 px
- Horizontal logo120 px widePrefer 32 px+ height
- Horizontal with descriptor160 px wideAvoid below 48 px height
- Stacked logo80 px widePrefer 72 px+ height
Print Recommended
- Icon only8 mmRecommended working value
- Horizontal logo25 mm wideRecommended working value
Actual-size previews
Icon mark rendered at true CSS pixel sizes inside equal frames. Prefer 24 px or larger.
Descriptor readability
Descriptor lockups become hard to read below 48 px height.
Logo in use
Approved Amevia assets in common product and marketing contexts.
Website header
Dark navigation
Dashboard sidebar
Login screen
Mobile app icon
Browser favicon
Presentation cover
Social avatar
Email signature
Partner footer
Powered by Amevia
Product card
Background tester
Check logo contrast against common surfaces. Photo and busy patterns are contrast tests only.
Background
Do / Don’t
Visual examples of correct application and common errors. Always start from official assets.
Do
Use official assets
Preserve proportions
Maintain clear space
Correct light / dark variant
Keep descriptor separate
Don’t
Do not stretch
Do not skew
Do not rotate
Do not recolor arbitrarily
Do not add unapproved shadows
Do not add glow to the static logo
Do not crop
Do not outline
Do not place on low contrast
Do not use “AmeviaAI” as one word
Do not permanently attach “AI” to the wordmark
Asset naming
Files under public/brand/ follow a consistent prefix and suffix convention. Consumers do not need to rename assets for normal use.
amevia-logo-horizontal.svgPrimary horizontal lockup for light backgroundsamevia-logo-horizontal-dark.svgPrimary horizontal lockup for dark backgroundsamevia-logo-stacked.svgStacked symbol + wordmarkamevia-logo-horizontal-tagline.svgHorizontal lockup with descriptoramevia-icon-gradient.svgSymbol only with brand gradientamevia-icon-black.svgMonochrome symbol for printamevia-wordmark-dark.svgWordmark only (dark type)
Suffixes: -dark / -light for background tone; -black / -white for monochrome; -tagline for descriptor lockups; icon- for symbol-only marks.
Common contexts: headers → amevia-logo-horizontal.svg; dark UI → amevia-logo-horizontal-dark.svg; favicons → amevia-icon-gradient.svg; print → amevia-icon-black.svg.
Future exports: keep the amevia- prefix, describe layout then tone, and never invent alternate brand spellings in filenames.
Animated logo treatments
Motion treatments are separate presentation assets and must not replace the approved static logo. The official logo remains static. Motion is contextual.
Ready to use Amevia?
Download the complete approved logo package, including SVG, PNG, monochrome, favicon and app-icon assets.
- Version 1.0
- Updated July 2026
- 137 files
- 3.7 MB
Color
The Amevia color system balances clarity, trust and energy through a refined palette of violet, indigo, blue and cyan, supported by deep navy foundations and accessible neutral scales.
Brand Colors
Core Amevia accents used for identity, motion and interactive emphasis.
Amevia Violet
Primary brand accent. Used for highlights and motion.
Amevia Indigo
Secondary brand color for focus rings, links on dark, and UI accents.
Amevia Blue
Gradient mid-point and interactive accents.
Amevia Cyan
Energetic accent and gradient end stop. Use sparingly.
Foundation Colors
Deep navy surfaces that anchor dark UI and inverse treatments.
Amevia Navy
Primary dark surface, wordmark on light, and inverse backgrounds.
Amevia Night
Dark-mode base and secondary navy surface.
Neutral Scale
Slate-aligned neutrals for text, borders and surfaces. Neutral 0 and 950 extend the official scale.
Neutral 0
Absolute white / inverse text on dark.
Neutral 50
Page and soft backgrounds.
Neutral 100
Secondary surfaces.
Neutral 200
Default borders.
Neutral 300
Strong borders and dividers.
Neutral 400
Placeholder and muted icons.
Neutral 500
Secondary text.
Neutral 600
Strong supporting text.
Neutral 700
Emphasized muted text.
Neutral 800
Dark elevated surfaces.
Neutral 900
Primary text on light.
Neutral 950
Deepest neutral foundation.
Semantic Colors
Status colors for success, warning, error and informational feedback.
Success
Positive actions and confirmations.
Warning
Cautions and attention states.
Error
Errors and destructive actions.
Info
Informational messages and tips.
Official gradients
Gradients aligned with the Amevia logo ribbon — violet through indigo, blue and cyan.
Primary Brand Gradient
Symbol fills, hero accents, and primary CTAs.
linear-gradient(135deg, #7C3AED 0%, #3B82F6 50%, #06B6D4 100%)radial-gradient(circle at 30% 20%, #7C3AED 0%, #3B82F6 45%, #06B6D4 100%)Secondary Gradient
Secondary marketing surfaces and product highlights.
linear-gradient(135deg, #4F46E5 0%, #3B82F6 55%, #06B6D4 100%)Dark Gradient
Dark sections, hero shells, and inverse panels.
linear-gradient(180deg, #071126 0%, #0A1430 100%)Hero Gradient
Full-bleed heroes aligned with logo ribbon energy.
linear-gradient(135deg, #7C3AED 0%, #4F46E5 35%, #2563EB 70%, #06B6D4 100%)Motion Glow Gradient
Motion treatments and soft glow accents — never on static logo marks.
linear-gradient(135deg, rgba(124,58,237,0.55) 0%, rgba(79,70,229,0.35) 50%, rgba(6,182,212,0.45) 100%)radial-gradient(circle at 50% 40%, rgba(124,58,237,0.55) 0%, rgba(6,182,212,0.15) 55%, transparent 75%)Soft Surface Gradient
Subtle card washes and section backgrounds.
linear-gradient(135deg, rgba(124,58,237,0.12) 0%, rgba(59,130,246,0.08) 50%, rgba(6,182,212,0.12) 100%)Color roles
Map tokens to common UI roles so product surfaces stay consistent.
Primary button--amevia-navy / --gradient-brand
Solid navy or brand gradient fill with inverse text.
Secondary button--surface-primary + --border-default
White surface with neutral border.
Link--text-link
Interactive text links on light surfaces.
Hover--amevia-indigo
Hover emphasis on brand controls.
Active--amevia-violet
Pressed / selected brand state.
Focus--border-focus
Focus ring for keyboard navigation.
Badge--amevia-indigo tint
Status and category badges.
Hero--gradient-dark / --gradient-hero
Hero shells and cover backgrounds.
Card--surface-primary
Default elevated content surface.
Navigation--amevia-navy / --surface-page
Sidebar and top navigation shells.
Borders--border-default
Dividers and control outlines.
Backgrounds--surface-page
Page canvas behind content.
Icons--amevia-indigo / currentColor
UI icons; prefer currentColor in components.
Accessibility
WCAG contrast checks for common Amevia pairings. Prefer AAA for body text where possible.
Aa
White on Navy
18.80:1AAA
18.80:1AAA
Aa
White on Violet
5.70:1AA
5.70:1AA
Aa
White on Blue
3.68:1Fail
3.68:1Fail
Aa
Navy on Neutral 50
17.97:1AAA
17.97:1AAA
Aa
Black on White
17.85:1AAA
17.85:1AAA
Aa
Success on White
3.77:1Fail
3.77:1Fail
Aa
Error on White
4.83:1AA
4.83:1AA
Light / Dark mode
Surfaces, text and chrome adapt through semantic tokens — primitives stay constant.
Light UI
AmeviaDocs
Card surface with primary text.
Success
Dark UI
AmeviaDocs
Card surface with inverse text.
Success
Token hierarchy
Prefer component and semantic tokens in product UI. Reach for primitives only when defining new semantics.
Primitive
--amevia-violet#7C3AED
Raw brand value from the palette.
Semantic
--text-brand / --border-focus#4F46E5
Intent-based alias for UI roles.
Component
--button-primary-bgvar(--amevia-navy)
Component-scoped mapping for buttons and chrome.
Color in use
Active preset: Light. Official light-surface tokensOfficial UI preview
See how Amevia’s approved colors work together across common interface patterns in light and dark themes.
Approved theme
Your website’s AI workforce.
Engage visitors, answer questions, and automate tasks with Amevia’s official color system — never arbitrary remixes.
Sign in to Amevia
Authentication using official light-surface tokens.
Info
Agent workspace
Feature card using surface, muted text, and semantic status chips.
Form controls
Agent online
Status treatments
SuccessWarningErrorInfo
1,284Conversations
326Leads captured
98%Resolution rate
Amevia Agent● Online
Hi — I can help visitors engage, answer questions, and automate tasks 24/7.
Color role summary
| Role | Token | Primitive | Usage |
|---|---|---|---|
| Primary | --color-primary | --amevia-indigo | Primary buttons, active states, key actions |
| Accent | --color-accent | --amevia-violet | Highlights, badges, selective emphasis |
| Surface | --surface-primary | --neutral-0 / --amevia-night | Cards, panels, elevated chrome |
| Background | --surface-page | --neutral-50 / --amevia-navy | Page canvas behind content |
| Text primary | --text-primary | --neutral-900 / --neutral-100 | Headings and body copy |
| Text muted | --text-muted | --neutral-500 / --neutral-400 | Supporting and secondary text |
| Border | --border-default | --neutral-200 / --neutral-800 | Dividers and control outlines |
| Focus | --border-focus | --amevia-indigo | Keyboard focus rings |
| Success | --color-success | --color-success | Confirmations and online status |
| Warning | --color-warning | --color-warning | Caution and attention states |
| Error | --color-error | --color-error | Errors and destructive actions |
| Info | --color-info | --color-info | Informational messages |
Accessibility status
- Text on page
17.06:1 · focus visibleAAA - Text on surface
17.85:1 · focus visibleAAA - Muted on surface
4.76:1 · focus visibleAA - Primary button
6.29:1 · focus visibleAA - Semantic states remain labeled by text, not color aloneOK
Correct usage
Incorrect
Random independent color choices create off-brand, low-trust combinations.
Correct
Approved Amevia theme using semantic tokens mapped to official primitives.
Semantic palettes
Extended scales for backgrounds, borders, text and solid fills. Step 500 matches the official solid token.
Success
Success 50
Tinted background
Success 100
Soft surface
Success 200
Border / soft fill
Success 300
Muted accent
Success 400
Supporting accent
Success 500
Solid fill / text on light
Success 600
Strong text / hover
Success 700
High-contrast text
Success 800
Deep accent
Success 900
Darkest solid
Warning
Warning 50
Tinted background
Warning 100
Soft surface
Warning 200
Border / soft fill
Warning 300
Muted accent
Warning 400
Supporting accent
Warning 500
Solid fill / text on light
Warning 600
Strong text / hover
Warning 700
High-contrast text
Warning 800
Deep accent
Warning 900
Darkest solid
Error
Error 50
Tinted background
Error 100
Soft surface
Error 200
Border / soft fill
Error 300
Muted accent
Error 400
Supporting accent
Error 500
Solid fill / text on light
Error 600
Strong text / hover
Error 700
High-contrast text
Error 800
Deep accent
Error 900
Darkest solid
Info
Info 50
Tinted background
Info 100
Soft surface
Info 200
Border / soft fill
Info 300
Muted accent
Info 400
Supporting accent
Info 500
Solid fill / text on light
Info 600
Strong text / hover
Info 700
High-contrast text
Info 800
Deep accent
Info 900
Darkest solid
Downloads
Export approved color tokens for engineering handoff. Figma variables are not published yet.
Do / Don’t
Do
- Aa
Maintain sufficient contrast for text and controls.
Use semantic colors consistently for status.
Use official gradients for brand moments.
- var(--)
Prefer design tokens over hard-coded hex.
Don’t
Random opacity changes that break contrast.
Unapproved neon gradients.
Random neon colors outside the system.
Replace brand violet with arbitrary substitutes.
Use semantic colors as branding accents.
Typography
Typography
Display that communicates with clarity.
Typography is one of Amevia's primary brand assets. The combination of Plus Jakarta Sans, Inter and IBM Plex Mono creates a modern, trustworthy and highly readable interface across marketing pages, applications and documentation.
Font system
Three roles, three families — keep Display for headlines, Inter for product UI, and Mono for technical values.
Plus Jakarta Sans
- Hero headlines
- Section titles
- Marketing pages
600700800
Your website’s AI workforce.
Inter
- Paragraphs
- UI
- Labels
- Navigation
- Forms
400500600
Engage visitors, answer questions and automate tasks 24/7.
IBM Plex Mono
- CSS variables
- Tokens
- Code
- JSON
- APIs
400500
--amevia-indigo: #4F46E5;
Type scale
Complete scale mapped to official CSS tokens. Specimens are capped in this table for readability — sizes still reference the real tokens.
Display XL
--text-display-xlHero statementsYour website’s AI workforce.
- Font
- Display
- Weight
- 800
- Size
- clamp(3rem, 6vw, 4.5rem)
- Line height
- 1.1
- Tracking
- -0.02em
Display L
--text-display-lCover titlesBuilt for every context
- Font
- Display
- Weight
- 700
- Size
- clamp(2.5rem, 5vw, 4rem)
- Line height
- 1.1
- Tracking
- -0.02em
Display M
--text-display-mFeature headlinesEngage. Answer. Automate.
- Font
- Display
- Weight
- 700
- Size
- clamp(2rem, 4vw, 2.75rem)
- Line height
- 1.15
- Tracking
- -0.02em
Heading 1
--text-h1Page titlesBrand overview
- Font
- Display
- Weight
- 700
- Size
- clamp(2rem, 4vw, 3rem)
- Line height
- 1.15
- Tracking
- -0.02em
Heading 2
--text-h2Section titlesOfficial UI preview
- Font
- Display
- Weight
- 600
- Size
- clamp(1.75rem, 3vw, 2.25rem)
- Line height
- 1.2
- Tracking
- -0.01em
Heading 3
--text-h3SubsectionsColor roles
- Font
- Display
- Weight
- 600
- Size
- clamp(1.375rem, 2.5vw, 1.75rem)
- Line height
- 1.25
- Tracking
- 0
Heading 4
--text-h4Card titlesAgent workspace
- Font
- Display
- Weight
- 600
- Size
- 1.25rem
- Line height
- 1.3
- Tracking
- 0
Body Large
--text-body-lgLead paragraphsAmevia helps visitors discover products, answer questions and complete meaningful actions in real time.
- Font
- Body
- Weight
- 400
- Size
- 1.125rem
- Line height
- 1.65
- Tracking
- 0
Body
--text-bodyDefault reading textAmevia helps visitors discover products, answer questions and complete meaningful actions in real time.
- Font
- Body
- Weight
- 400
- Size
- 1rem
- Line height
- 1.5
- Tracking
- 0
Body Small
--text-body-smSupporting copyEngage visitors, answer questions and automate tasks 24/7.
- Font
- Body
- Weight
- 400
- Size
- 0.875rem
- Line height
- 1.5
- Tracking
- 0
Caption
--text-captionMetadata and hintsUpdated July 2026
- Font
- Body
- Weight
- 400
- Size
- 0.75rem
- Line height
- 1.4
- Tracking
- 0.02em
Overline
--text-overlineEyebrows and labelsLogo system
- Font
- Body
- Weight
- 600
- Size
- 0.75rem
- Line height
- 1.4
- Tracking
- 0.12em
Button
--text-buttonControls and CTAsStart conversation
- Font
- Body
- Weight
- 600
- Size
- 0.875rem
- Line height
- 1
- Tracking
- 0
Code
--text-codeTokens and snippets--font-display
- Font
- Mono
- Weight
- 500
- Size
- 0.8125rem
- Line height
- 1.5
- Tracking
- 0
Font weight preview
Switch weights on a live Plus Jakarta Sans specimen. Approved Display weights are 600–800.
Your website’s AI workforce.
Responsive behavior
Display sizes use fluid clamp values. Preview the same headline across breakpoints.
Your website’s AI workforce.
Amevia helps visitors discover products, answer questions and complete meaningful actions in real time.
Character set
Supported characters for brand and product surfaces, including Romanian diacritics.
Uppercase
ABCDEFGHIJKLMNOPQRSTUVWXYZ
Lowercase
abcdefghijklmnopqrstuvwxyz
Numerals
0123456789
Symbols
!@#$%^&*()
Romanian
Ă Â Î Ș Ț ă â î ș ț
German
Ä Ö Ü ß ä ö ü
French
À Â Æ Ç É È Ê Ë Î Ï Ô Œ Ù Û Ü Ÿ
Spanish
Á É Í Ó Ú Ü Ñ ¿ ¡
Currency
€ $ £ ¥
Mathematical
→ ← × ÷ ±
Font pairing
Realistic pairings for marketing, product, chat and docs.
Marketing hero
Your website’s AI workforce.
Amevia helps visitors discover products, answer questions and complete meaningful actions in real time.
Dashboard
Conversations
Last 7 days
1,284 conversations resolved with a 98% success rate.
Chat widget
Amevia Agent
Hi — I can help visitors engage, answer questions, and automate tasks 24/7.
Just now
Documentation
Token hierarchy
Prefer semantic tokens in product UI. Reach for primitives only when defining new roles.
--color-primary: var(--amevia-indigo);Text examples
Amevia product copy — not placeholder lorem.
Headline
Your website’s AI workforce.
Paragraph
Amevia helps visitors discover products, answer questions and complete meaningful actions in real time.
Button
Start conversation
Label
Visitor email
Status
Agent online
Code tokens
Real CSS custom properties from styles/tokens.css.
--font-display"Plus Jakarta Sans", ui-sans-serif, system-ui, sans-serif--font-body"Inter", ui-sans-serif, system-ui, sans-serif--font-mono"IBM Plex Mono", ui-monospace, monospace--weight-light300--weight-regular400--weight-medium500--weight-semibold600--weight-bold700--weight-extrabold800--text-display-xlclamp(3rem, 6vw, 4.5rem)--text-display-lclamp(2.5rem, 5vw, 4rem)--text-display-mclamp(2rem, 4vw, 2.75rem)--text-h1clamp(2rem, 4vw, 3rem)--text-h2clamp(1.75rem, 3vw, 2.25rem)--text-h3clamp(1.375rem, 2.5vw, 1.75rem)--text-h41.25rem--text-body-lg1.125rem--text-body1rem--text-body-sm0.875rem--text-caption0.75rem--text-overline0.75rem--text-button0.875rem--text-code0.8125rem--leading-tight1.1--leading-normal1.5--leading-relaxed1.65--tracking-tight-0.02em--tracking-tagline0.12emTypography accessibility
Recommendations
- ✓ Recommended minimum body size: 16px (1rem)
- ✓ Recommended contrast: AA+ for body, AAA preferred for long reading
- ✓ Comfortable line length: 65–75 characters
- ✓ Minimum line height: 1.5 for body
- ✓ Avoid ALL CAPS for long paragraphs
Amevia defaults
- ✓ Body uses Inter at 16px / 1.5
- ✓ Display tracking stays tight for large sizes only
- ✓ Overlines use wide tracking and short labels
- ✓ Mono reserved for technical values
Best practices
Do
- ✓ Keep body between 16–18px
- ✓ Use Display only for headings
- ✓ Use Inter for UI
- ✓ Use Mono for code
Don’t
- ✕ Mix multiple display fonts
- ✕ Stretch fonts
- ✕ Use excessive letter spacing
- ✕ Use ALL CAPS for paragraphs
Live preview
A realistic product shell using only the official typography system — no arbitrary controls.
AmeviaProduct · Docs · Pricing
Your website’s AI workforce.
Amevia helps visitors discover products, answer questions and complete meaningful actions in real time.
Amevia Agent
I can help visitors engage, answer questions, and automate tasks 24/7.
Agent online · Just now
Conversations
1,284
Last 7 days
Token
--font-displayVisual language
A visual system built around clarity, spacious layouts, subtle motion and premium SaaS aesthetics.
Principles
Six foundations of the Amevia visual system — each with a live example.
Shape language
Soft rounded forms echoing the logo ribbon. 8–24px radius system.
Spacing
4px grid with generous section gaps. Breathing room is premium.
4
8
12
16
24
32
48
64
96
Motion
150–400ms transitions. Purposeful, calm, and reduced-motion aware.
Button
Card lift
Fade
Fast · 150msNormal · 250msSlow · 400ms
Shadows
Navy-tinted elevation. Subtle depth, never harsh.
Gradients
Brand ribbon energy for accents. Soft washes for surfaces — never on body text.
Primary ribbon
Background wash
Accent glow
Surface gradient
Iconography
24px grid, 1.75px stroke, rounded caps. Outlined by default in brand indigo.
Layout system
Responsive grids with consistent margins, gutters and container widths.
Desktop · 12 columns
Max width 1200px · gutter 24px · margin 32–64px
Tablet · 8 columns
Gutter 16–20px · margin 24px
Mobile · 4 columns
Gutter 12–16px · margin 16px
Component style
Visual recipes for common product chrome.
Buttons
Cards
Elevated surface with soft shadow
Inputs
Badges
OnlineTables
| Metric | Value |
|---|---|
| Leads | 326 |
Navigation
AmeviaDocs
Depth
Elevation layers for calm hierarchy.
Layer 0
Background
Layer 1
Cards
Layer 2
Dropdown
Layer 3
Modal
Layer 4
Notifications
Surface language
Official surfaces for light product UI and dark shells.
Primary background--surface-page
Secondary surface--surface-primary
Glass surfaceFrosted overlay
Dark surface--amevia-navy
Gradient surface--gradient-brand
Interactive surfaceFocus-ready control
Motion examples
Calm previews. Animations pause when reduced motion is preferred.
Card hover
Button hover
Loading
Fade
Ribbon glow
Success
Illustration style
Do
- ✓ Abstract gradients
- ✓ Geometric shapes
- ✓ Product UI
- ✓ Soft lighting
- ✓ Premium SaaS
Don’t
- ✕ Robots
- ✕ Brains
- ✕ AI chips
- ✕ Wireframe humans
- ✕ Stock / sci-fi clichés
Photography
Preferred
- ✓ Modern workspace
- ✓ Premium offices
- ✓ Screens and product UI
- ✓ Minimal setups
Avoid
- ✕ Corporate handshakes
- ✕ Smiling call centers
- ✕ Fake AI imagery
UI examples
Amevia inside miniature product frames.
Animation philosophy
Purposeful
Motion explains state change — never decoration for its own sake.
Responsive
Feedback feels immediate within 150–250ms for most interactions.
Calm
Soft easing, limited travel, and respect for reduced motion.
Brand feel
Emotional descriptors expressed through approved gradients.
ConfidentHelpfulPremiumFastTrustworthyModernCalm
Visual do / don’t
Do
- ✓ Spacious layouts
- ✓ Soft shadows
- ✓ Rounded corners
- ✓ Consistent gradients
Don’t
- ✕ Heavy shadows
- ✕ Sharp corners
- ✕ Busy layouts
- ✕ Multiple accent colors
- ✕ AI clichés
Motion & effects
Motion gives Amevia a sense of intelligence and flow without compromising clarity. Every effect should feel calm, purposeful and closely connected to the approved symbol.
PurposefulMotion explains state, direction or hierarchy.
RestrainedEffects support the interface without demanding attention.
AccessibleEvery treatment includes a static or reduced-motion alternative.
Ribbon Flow
RecommendedA broad moving light illuminates the Amevia ribbon in sequence, creating a continuous internal flow while keeping the symbol itself fixed.
Homepage hero · Product launch · Presentation cover
- 8-second default loop
- Subtle internal bloom
- Maximum breathing scale: 1.012
- Static reduced-motion fallback
Intensity
Speed
Background
Reduced motionSimulate accessibility fallback
Developer diagnostics
Show guide pathInspect the invisible travel path
Static fallback / assets
Responsive test
Continuous motion is recommended from 64 px upward. Use a static or one-time treatment below 64 px.
Secondary treatments
Supporting effects for loading, entrance, and static contexts.
Ribbon Sweep
One-timeA single highlight passes through the symbol, then rests.
Login · onboarding · launch screens
Soft Pulse
ContinuousA gentle internal brightness and scale pulse for loading and idle states.
Loading · idle · empty states
Static Glow
StaticA non-animated close bloom for persistent UI and reduced-motion contexts.
Navigation · dense screens · reduced motion
Reveal
One-timeA one-time fade, scale and light-sweep entrance.
Page load · chat launcher open
Use-case matrix
Recommended treatments by product context.
| Context | Recommended effect | Intensity | Loop behavior |
|---|---|---|---|
| Homepage hero | Ribbon Flow | Hero | Continuous |
| Navigation | Static Glow | Subtle | Static |
| Loading | Soft Pulse | Standard | Continuous |
| Login / onboarding | Ribbon Sweep | Standard | One-time or periodic |
| Chat launcher | Reveal | Subtle | One-time |
| Presentation cover | Ribbon Flow | Standard | Continuous |
| Favicon | None | — | Static |
| Dense UI | Static Glow or none | Subtle | Static |
- Homepage heroRibbon FlowHeroContinuous
- NavigationStatic GlowSubtleStatic
- LoadingSoft PulseStandardContinuous
- Login / onboardingRibbon SweepStandardOne-time or periodic
- Chat launcherRevealSubtleOne-time
- Presentation coverRibbon FlowStandardContinuous
- FaviconNone—Static
- Dense UIStatic Glow or noneSubtleStatic
Homepage hero preset
The recommended flagship composition combines Ribbon Flow, a close inner bloom and restrained breathing motion.
Loading & small-size presets
48–96 px: Soft Pulse · Chat launcher: one-time Reveal or Sweep · Below 32 px: static icon only
Agent mark · 48 px
Interactive playground
Compose a treatment and copy the generated component usage.
Effect
Size
Background
Intensity
Speed
Hover
Reduced motion
Pause
<AnimatedAmeviaIcon
effect="ribbon-flow"
size={200}
intensity="hero"
background="dark"
interactive
/>Usage guidance
Recommended
- Homepage hero
- Loading and onboarding
- Presentation covers
- One-time chat-launcher reveal
Avoid
- Persistent navigation animation
- Favicons
- Dense tables and forms
- Spinner-like treatment
- Multiple effects at once
Timing
- Ribbon Flow: 8s default
- Sweep: 1.5s with a 5–8s pause
- Reveal: under 1.2s
- Breathing: maximum scale 1.012
Motion tokens
Shared durations and easing aliases used across UI chrome and brand motion.
| Token | Value | Use | Copy |
|---|---|---|---|
--motion-fast | 150ms | UI chrome transitions | |
--motion-standard | 250ms | Default interface motion | |
--motion-slow | 400ms | Emphasis transitions | |
--motion-ease-out | cubic-bezier(0, 0, 0.2, 1) | Decelerating exits and settles | |
--motion-ease-in-out | cubic-bezier(0.4, 0, 0.2, 1) | Symmetric UI easing | |
--motion-breathe-scale | 1.012 | Recommended max breathing scale | |
--motion-ribbon-duration | 8s | Ribbon Flow default loop | |
--motion-sweep-duration | 7s | Ribbon Sweep cycle (pass + pause) |
Motion should feel
CalmSmooth transitions, no bounce.
PurposefulMotion communicates state or emphasis.
LocalGlow stays close to the symbol or component.
ConsistentThe same durations and easing patterns are reused.
Never: flashy · game-like · neon-heavy · spinner-like · continuously distracting
Voice & tone
Amevia communicates with clarity, warmth and confidence. Every message should help people understand what is happening, what they can do next and when human support may be more appropriate.
Clear, helpful and human — never vague, exaggerated or robotic.
Voice vs tone
Voice
The consistent personality Amevia uses everywhere.
- Clear
- Helpful
- Calm
- Confident
- Human
- Concise
- Transparent
Tone
How that voice adapts to the user’s context, intent and emotional state.
- context
- urgency
- user confidence
- task complexity
- risk
- channel
Core voice principles
Seven attributes that stay consistent across every Amevia surface.
Use plain language and explicit next steps.
Connect your website to start reviewing imported content.
Move the visitor toward an answer or useful action.
I found three relevant options. Would you like to compare them?
Remain composed, especially when something goes wrong.
We couldn’t load this information. Please try again.
Be direct without sounding absolute or arrogant.
Amevia helps visitors find answers and take useful next steps.
Sound natural and considerate, not scripted.
Hi, I’m Amevia. How can I help?
Say enough to be useful, then stop.
Your changes have been saved.
Acknowledge uncertainty, limitations and handoffs.
I’m not fully confident I found the right answer. Would you like to contact the team?
Do / don’t
Paired examples that show the same idea written the Amevia way.
DoAmevia helps visitors find answers and take useful next steps.
Don’tAmeviaAI will revolutionize your business with superhuman intelligence!
States the benefit plainly without hype or invented brand names.
DoConnect your website and begin reviewing imported content.
Don’tLaunch your perfect AI agent instantly with zero setup.
Sets a realistic action and expectation instead of an impossible promise.
DoI found a few relevant options. Would you like to compare them?
Don’tThese are definitely the perfect products for you.
Offers guidance while leaving the decision with the visitor.
DoI’m not fully confident that I found the right answer. Would you like to contact the team?
Don’tI know everything about this website.
Honesty about limits builds trust and opens a useful handoff.
DoSomething went wrong while loading this information. Please try again.
Don’tOops! The AI broke.
Names the problem calmly and gives a recovery step.
DoYour changes have been saved.
Don’tSuccess! Everything is absolutely perfect now!
Confirms the outcome without theatrical language.
DoThis action requires confirmation before it can continue.
Don’tJust click here and let Amevia handle everything automatically.
Respects consent and avoids false automation claims.
DoA human support specialist can help with this request.
Don’tI cannot help you.
Ends with a constructive path instead of a dead end.
Tone by context
How the same voice adapts across channels and situations.
Marketing website
Confident, concise, benefit-led
Engage visitors, answer questions, automate tasks and take action 24/7.
Avoid: Revolutionary AI that transforms everything overnight.
Product interface
Direct, functional, predictable
Connect your website to begin building your Amevia agent.
Avoid: Let’s unlock the magic of your digital workforce!
Chat agent
Helpful, conversational, adaptive
Hi, I’m Amevia. How can I help?
Avoid: GREETINGS HUMAN. INITIATING ASSISTANCE PROTOCOL.
Documentation
Precise, instructional, complete
Install the snippet before the closing </body> tag on every page you want the agent to appear.
Avoid: Just drop the thing somewhere on your site.
Sales
Outcome-focused, credible, never pressured
Turn website conversations into actions — without rebuilding your site.
Avoid: Act now before this limited offer expires!
Customer support
Patient, empathetic, action-oriented
I’ve reviewed the available information. Here is what I found.
Avoid: As previously stated, please re-read the documentation.
Errors
Calm, specific, recovery-focused
We couldn’t complete this action. Please try again.
Avoid: Fatal exception. Something exploded.
Security and privacy
Serious, transparent, reassuring
We need to verify this action before continuing.
Avoid: Don’t worry — nothing bad will ever happen.
Social media
Clear, energetic, approachable
Meet Amevia — an AI agent platform designed to make website conversations more useful.
Avoid: 🔥🚀 #AI #Disruption #GameChanger
Professional, concise, context-aware
Your Amevia website connection is ready.
Avoid: YOU WON’T BELIEVE WHAT YOUR AGENT CAN DO!!!
The Amevia agent voice
The agent should feel like a helpful guide — direct, honest, and ready to hand off when needed.
- Start in the detected website language
- Adapt to the visitor’s language when they switch
- Answer directly before adding details
- Avoid pretending to know unavailable information
- Distinguish confirmed facts from assumptions
- Offer useful next actions
- Escalate to a human when confidence is low
- Avoid repeated greetings
- Avoid excessive emojis
- Avoid overly long answers
- Never pressure users into a purchase
GreetingHi, I’m Amevia. How can I help?
Product discoveryWhat are you looking for, and which features matter most?
RecommendationI found three relevant options based on your requirements.
UncertaintyI’m not fully confident that this information is current. Would you like me to help you contact the team?
Human handoffA member of the team would be better placed to help with this request.
Action confirmationWould you like me to add this item to your cart?
Response structure
1. Direct answer2. Relevant supporting detail3. Clear next step4. Optional human handoff
Yes, this product is available in blue. It is currently listed in two sizes. Would you like to view the product page or compare the sizes?
Keep responses naturally flexible; do not force this structure where it is unnecessary.
How Amevia communicates uncertainty
Confidence must never be implied when the source information is incomplete.
Approved phrases
- Based on the available information…
- I found a likely match…
- I’m not fully confident this is the correct answer…
- This information may need confirmation…
- A member of the team can verify this for you.
Avoid
- Definitely
- Guaranteed
- Always
- Never
- Perfect
- I know
- Zero risk
- Zero errors
Microcopy system
Prefer specific labels. Avoid vague words like Submit, Okay, Click here, or Error occurred.
Buttons
- Continue
- Save changes
- View product
- Contact the team
- Try again
Empty states
- No conversations yet
- No knowledge sources connected
- No matching products found
Loading
- Checking available information…
- Searching connected sources…
- Preparing your recommendations…
Success
- Changes saved
- Website connected
- Knowledge source added
Errors
- We couldn’t complete this action.
- Please check the connection and try again.
- This information is temporarily unavailable.
Confirmation
- Remove this knowledge source?
- This action cannot be undone.
Tone adaptation
The same message shifts with the user’s emotional state and risk level.
Your changes have been saved.
Here’s what this setting controls, and what happens when you turn it on.
Sorry this didn’t work. Let’s try another way to get you what you need.
We couldn’t complete checkout. Please try again or contact support.
This action needs verification. A team member can help you continue securely.
Based on what you described, this option may fit. Would you like a short comparison?
Language and localization
- Write naturally in each language
- Do not translate word-for-word when it sounds unnatural
- Preserve meaning and tone
- Use regionally appropriate punctuation and formats
- Avoid idioms that do not translate well
- Keep product names and approved terminology consistent
- Detect the website language before the initial greeting
- Adapt after the visitor writes in another language
Useă â î ș ț
Avoidş ţ
Use Romanian diacritics with comma-below characters, not legacy cedillas.
Style rules
Use sentence case for headings, buttons and labels unless a specific component requires uppercase.
Allowed in conversational and marketing contexts where natural.
Rare and contextual. Avoid in enterprise UI, errors, security and legal communication.
Use sparingly. Never stack multiple exclamation marks.
Prefer short complete sentences.
Use numerals for metrics, dates and technical values.
Use Amevia, Amevia agent, Amevia platform. Avoid AmeviaAI, AMEVIA in body copy, and unnecessary title case.
Before / after
BeforeOur revolutionary autonomous AI solution will transform your online business.
AfterAmevia helps visitors find answers, discover relevant options and take useful actions.
BeforeOops! Something went wrong.
AfterWe couldn’t load this information. Please try again.
BeforeSubmit
AfterSave changes
BeforeThe chatbot cannot answer your question.
AfterI’m not confident I found the right answer. A member of the team can help.
Channel-specific examples
Your website’s AI workforce.
Engage visitors, answer questions, automate tasks and take action 24/7.
Connect a website to begin building your Amevia agent.
Hi, I’m Amevia. What can I help you find?
I’ve reviewed the available information. Here is what I found.
We need to verify this action before continuing.
Your Amevia website connection is ready
Meet Amevia — an AI agent platform designed to make website conversations more useful.
Content checklist
Before publishing, confirm that the copy:
- Answers the user’s likely question
- Uses plain language
- Includes a useful next step
- Avoids unsupported claims
- Acknowledges uncertainty where needed
- Matches the context
- Remains concise
- Sounds natural when read aloud
Deep dive
Explore the complete voice and tone guide
Review detailed writing principles, channel guidance, agent-response patterns, localization and approved terminology.
Messaging
A consistent messaging framework ensures Amevia communicates the same core value across every touchpoint while adapting the depth and detail to different audiences.
Messaging hierarchy
Start from the core promise, then choose the depth that fits the surface — from a six-word tagline to a full company description.
1
Core brand promise
Turn website conversations into useful actions.
Internal north star · strategy · brand reviews
2
Primary tagline
Your website’s AI workforce.
Homepage · hero · brand assets · events
3
Value statement
Engage visitors, answer questions, automate tasks and take action 24/7.
Landing pages · product pages · campaigns
4
Positioning
More than chat. Useful actions for every website.
Competitive comparisons · sales · overview pages
5
One-sentence description
Amevia is an intelligent website agent that helps visitors find answers, discover products and take useful actions.
Metadata · directory listings · app stores · partner pages
6
Elevator pitch
Amevia gives websites intelligent agents that answer questions, recommend products, capture leads and trigger actions while integrating with existing websites.
Sales · investors · media · partners
7
Long-form company description
Amevia is a SaaS platform that adds intelligent AI agents to any website. Visitors get helpful guidance — answers, product recommendations, lead capture, and connected actions. Businesses get better engagement without rebuilding their site. Amevia integrates with existing platforms, supports multiple languages, and is designed for online stores, service businesses, agencies, and hosting providers.
About pages · press kits · investor materials
Primary messages
Approved lines with recommended usage surfaces.
Primary tagline
Your website’s AI workforce.
HomepageHeroBrand assetsEvents
Value statement
Engage visitors, answer questions, automate tasks and take action 24/7.
Landing pagesProduct pagesCampaigns
Secondary message
Help every visitor find the right answer and take the next step.
ProductDocumentationSupport
Positioning
More than chat. Useful actions for every website.
Competitive comparisonsSalesOverview pages
One sentence
Amevia is an intelligent website agent that helps visitors find answers, discover products and take useful actions.
MetadataDirectory listingsApp storesPartner pages
Elevator pitch
Amevia gives websites intelligent agents that answer questions, recommend products, capture leads and trigger actions while integrating with existing websites.
SalesInvestorsMediaPartners
Message lengths
Pick a length that matches the available space and attention.
Your website’s AI workforce.
Hero · social · lockups
Help every visitor find answers and take useful actions.
Subheads · feature intros
Amevia helps visitors find answers, discover relevant options and take useful actions — without rebuilding your website.
Landing blurbs · partner blurbs
Amevia is an intelligent website agent that answers questions, recommends products, captures leads and triggers actions. It works with existing websites and helps every visitor find a useful next step.
Product summaries · sales one-pagers
Amevia gives every website an intelligent agent that understands content, guides visitors, and connects conversations to real outcomes. Visitors get clear answers and recommendations. Businesses get better engagement, leads and support coverage — without replacing their stack or rebuilding their site.
About snippets · marketplace listings
Amevia is a SaaS platform that adds intelligent AI agents to any website. Visitors get helpful guidance — answers, product recommendations, lead capture, and connected actions. Businesses get better engagement without rebuilding their site. Amevia integrates with existing platforms, supports multiple languages, and is designed for online stores, service businesses, agencies, and hosting providers.
Company overview · press · investor packs
Messaging by audience
Adapt the same promise to what each audience cares about most.
Website owners
Main concern
Visitors leave without converting or finding answers.
Key benefit
An agent that guides visitors and captures intent 24/7.
Recommended messaging
Help every visitor find the right answer and take the next step.
Connect your website
Developers
Main concern
Complex installs and brittle custom AI builds.
Key benefit
Clean integration with existing sites and workflows.
Recommended messaging
Add an intelligent website agent without rebuilding your stack.
View documentation
Marketing teams
Main concern
Campaigns drive traffic that still needs guidance.
Key benefit
Consistent on-site conversations that convert interest into action.
Recommended messaging
Turn website conversations into useful actions across every visit.
Explore features
Agencies
Main concern
Clients need better engagement without custom builds.
Key benefit
Deployable agents that fit client sites and brands.
Recommended messaging
Give every client site an intelligent agent they can launch quickly.
See partner options
Enterprise
Main concern
Governance, reliability and integration risk.
Key benefit
Controlled experiences with handoff, multilingual support and integrations.
Recommended messaging
Production-ready website intelligence that fits existing platforms and teams.
Book a demo
Support teams
Main concern
Repetitive questions and after-hours coverage.
Key benefit
Deflect common questions and escalate when confidence is low.
Recommended messaging
Answer common questions automatically and hand off when a person is needed.
Learn more
Partners
Main concern
Clear value story for joint go-to-market.
Key benefit
A credible website-agent layer to bundle with hosting or services.
Recommended messaging
Offer customers an AI agent platform designed for real website outcomes.
Explore integrations
Investors
Main concern
Category clarity and differentiated product story.
Key benefit
A focused website-agent platform between widgets and custom AI builds.
Recommended messaging
Amevia sits between simple chat widgets and complex custom AI builds.
Read company overview
Feature messaging
How Amevia talks about major capabilities.
An intelligent agent for every website
Guide visitors with context from your content and catalogue.
See how it worksAnswers grounded in your content
Connect pages, docs and sources so responses stay relevant.
Connect sourcesSuggest the next useful option
Help visitors discover products and services that match their needs.
Explore recommendationsCapture intent when it matters
Collect details and route qualified conversations to your team.
Start capturing leadsSee what visitors need
Track conversations, outcomes and opportunities across your site.
View analyticsConnect conversations to actions
Trigger workflows that move visitors forward without manual steps.
Explore automationsFits the stack you already use
Connect tools and platforms without rebuilding your website.
See integrationsEscalate when a person should help
Keep trust high by handing off when confidence is low.
Configure handoffMeet visitors in their language
Start in the site language and adapt when visitors switch.
Enable languagesFrom answers to outcomes
Help visitors view products, book, contact or continue a task.
Explore actionsPositioning against chatbots
Explain category differences without naming competitors. Amevia is more than FAQ chat.
Scripted replies with limited connection to site actions.
Useful references, but visitors must hunt for answers.
Finds pages when visitors already know what to type.
Helpful guidance, often still disconnected from outcomes.
An intelligent website agent that answers, recommends, captures leads and triggers useful actions.
Approved claims
✓ ApprovedHelps visitors find answers.
✓ ApprovedWorks with existing websites.
✓ ApprovedSupports multilingual experiences.
✓ ApprovedCaptures leads.
✓ ApprovedRecommends products.
✓ ApprovedConnects to website actions.
✓ ApprovedIntegrates into existing workflows.
Claims to avoid
✕ AvoidPerfect AIOverclaims accuracy and invites distrust.
✕ AvoidHuman replacementAmevia assists; people remain essential.
✕ AvoidZero hallucinationsNo system can guarantee zero errors.
✕ AvoidKnows everythingKnowledge is limited to connected sources.
✕ Avoid100% accurateAbsolute claims are unverifiable and risky.
✕ AvoidInstant salesOutcomes depend on offer, traffic and experience.
✕ AvoidAutonomous foreverOversells independence from teams and oversight.
✕ AvoidFully magicalHype language weakens clarity and credibility.
CTA library
Approved call-to-action wording, hierarchy and context. Prefer Start free as the default marketing conversion. Visual samples only show message hierarchy — button specs live in UI Components.
Primary conversion CTA
MarketingDrive the main signup or trial action for general visitors. One preferred default; alternatives are contextual only.
- Where it appears
- Homepage hero, pricing, campaign landings, product launch pages
- Avoid
- Treating every option as equal, or using vague “Get started” language
- Start freeRecommended
- Try AmeviaContextual
- Connect websiteContextual
Supporting CTA
MarketingHelp visitors learn without competing with the primary conversion. Keep secondary intent visually and linguistically quieter.
- Where it appears
- Hero secondary slots, feature sections, mid-page modules
- Avoid
- Matching primary weight, or using secondary labels as the main offer
- Learn moreContextual
- Explore featuresRecommended
- See integrationsRecommended
- View documentationDocumentation
- Read guideDocumentation
- Compare plansRecommended
- View pricingRecommended
Product action CTA
ProductOperational labels inside the product. Explicit, verb-led, task-specific and predictable.
- Where it appears
- Dashboard, settings, empty states, wizards, toolbars
- Avoid
- Marketing hype, vague verbs, or reusing conversion CTAs for routine tasks
- Connect websiteProduct
- Add knowledge sourceProduct
- Train agentProduct
- Preview widgetProduct
- Publish agentProduct
- Configure agentProduct
- Add integrationProduct
- Invite teammateProduct
- Save changesProduct
- Try againProduct
- Contact supportProduct
Sales CTA
SalesRoute high-intent or enterprise prospects into a sales conversation. Not the default for general visitors.
- Where it appears
- Enterprise pages, partner pages, larger pricing tiers, high-intent sales flows
- Avoid
- Using Book a demo as the default homepage primary for all visitors
- Book a demoSales
Documentation CTA
DocumentationGuide readers into technical or instructional content without implying signup.
- Where it appears
- Docs hub, API pages, developer footers, help modules
- Avoid
- Conversion language that implies signup when the goal is reading
- View documentationDocumentation
- API referenceDocumentation
- Read guideDocumentation
Chat and agent CTA
ChatConversational next steps shown by the agent. Describe the immediate action clearly.
- Where it appears
- Chat widget suggestions, agent message actions, product cards in chat
- Avoid
- Vague labels or marketing slogans inside the conversation
- View productRecommended
- Compare optionsRecommended
- Add to cartRecommended
- Check availabilityRecommended
- Book appointmentRecommended
- Contact the teamRecommended
- Talk to a personRecommended
- ContinueContextual
- Go backContextual
Destructive / confirmation CTA
SystemConfirm irreversible or high-impact actions. Pair a clear primary with a safe secondary cancel path.
- Where it appears
- Delete dialogs, discard prompts, disconnect confirmations
- Avoid
- Cute or vague wording; never hide the consequence
- Delete sourceProduct
- DiscardProduct
- CancelProduct
- DisconnectProduct
Removed from approved primary set: Avoid Get started — duplicates Start free and is less specific.
CTA copy rules
Do
- Begin with a clear verb
- Describe the result
- Use sentence case
- Keep labels concise
- Match the user’s current task
- Distinguish primary from secondary intent
Avoid
- Click here
- Submit
- Proceed
- Okay
- Next step
- Continue now
- Unlock
- Revolutionize
- Experience the future
- Let Amevia do everything
- Vague or exaggerated language
Get startedClick hereSubmitProceedOkayNext stepContinue nowUnlockRevolutionizeExperience the futureLet Amevia do everything
“Continue” is acceptable only when the next step is already obvious from the surrounding context.
CTA by context
- Homepage heroPrimary Start freeSecondary Book a demo
- PricingPrimary Start freeSecondary Compare plans
- OnboardingPrimary Connect websiteSecondary Skip for now
- Dashboard empty statePrimary Connect websiteSecondary View guide
- DocumentationPrimary View documentationSecondary API reference
- IntegrationsPrimary Connect integrationSecondary Learn more
- Chat widgetPrimary View productSecondary Contact the team
- Error statePrimary Try againSecondary Contact support
- Unsaved changesPrimary Save changesSecondary Discard
- Destructive confirmationPrimary Delete sourceSecondary Cancel
Before / after
Before
Get started
After
Start free
States the offer clearly — free trial — instead of a generic next step.
Before
Submit
After
Connect website
Names the outcome of the form, not the UI control.
Before
Click here
After
View documentation
Tells readers what they will open.
Before
Proceed
After
Publish agent
Makes the irreversible action explicit.
Before
Learn more
After
See integrations
Prefer a destination-specific label when the page is known.
Before
Next
After
Review configuration
Describes the upcoming step instead of a sequence number.
Before
Okay
After
Close
Confirms the dismissal action without ambiguity.
Before
Unlock the power of AI
After
Try Amevia
Drops hype and keeps a concrete, brand-clear action.
Channel examples
Your website’s AI workforce.
Engage visitors, answer questions, automate tasks and take action 24/7.
Choose the plan that fits your website — then connect and go live.
Hi, I’m Amevia. How can I help?
Install the snippet, connect your sources, and review your first conversations.
Connect a website to begin building your Amevia agent.
Your Amevia website connection is ready.
Meet Amevia — an AI agent platform designed to make website conversations more useful.
Amevia helps website visitors find answers, discover options and take useful next steps.
Amevia is an intelligent website agent platform that connects conversations to real actions.
Amevia: intelligent website agents for support, discovery, recommendations and lead capture.
Add an intelligent website agent that answers questions and drives useful actions.
SEO descriptions
Approved lengths for search, social and marketplace listings.
Intelligent website agents by Amevia
Amevia — your website’s AI workforce
Amevia helps visitors find answers, discover products and take useful actions on any website.
Amevia is an intelligent website agent that answers questions, recommends products, captures leads and triggers actions — without rebuilding your site.
Your website’s AI workforce. Engage visitors, answer questions, automate tasks and take action 24/7.
Meet Amevia — intelligent website agents that turn conversations into useful actions.
Add Amevia to guide visitors, capture leads and connect conversations to website actions.
FAQ messaging
Amevia is an intelligent website agent that helps visitors find answers, discover options and take useful actions.
Amevia goes beyond FAQ chat — it recommends, captures leads and connects conversations to website actions.
No. Amevia handles common questions and hands off to your team when a person should help.
Yes. Amevia can suggest relevant products or services based on visitor needs and your catalogue.
Yes. Amevia can collect visitor details and route qualified conversations to your team.
Yes. Amevia is designed to work with existing websites, platforms and workflows.
Terminology
Preferred
- Website agent
- Knowledge source
- Recommendation
- Conversation
- Lead
- Action
- Integration
Avoid
- Bot
- Magic
- Brain
- Superhuman
- Autonomous AI
- Perfect AI
Before / after
BeforeAI that revolutionizes everything.
AfterAI that helps visitors find answers and take useful actions.
BeforeThe smartest chatbot.
AfterAn intelligent website agent.
BeforeFully autonomous AI with zero errors.
AfterA website agent that answers common questions and hands off when needed.
BeforeMagic that sells for you.
AfterGuidance that helps visitors discover options and take the next step.
BeforeAmeviaAI — superhuman intelligence.
AfterAmevia — your website’s AI workforce.
BeforeReplace your support team today.
AfterExtend support coverage and escalate to people when confidence is low.
BeforeGuaranteed 10x conversions.
AfterTurn more website conversations into useful actions.
BeforeThe most advanced AI on the planet.
AfterProduction-ready website intelligence that fits your existing site.
Messaging toolkit
Download Markdown references for guides, copy decks, SEO, elevators and press boilerplate. Print this Brand Book section for a PDF-ready messaging pack.
UI components
Representative production UI components showing approved appearance, behavior, interaction states and accessibility guidelines. Every product should reuse these patterns instead of creating custom variants.
Input system
Labels above fields. Helper text below. Errors use aria-invalid and linked messages.
ReactTailwindCSS VariablesAccessibleDark ModeResponsive
Text field
Email field
Password field
Search field
Website URL field
Number field
Date field
File uploadUpload knowledge source files for your agent.
No file selectedPDF, CSV, TXT or MD · max 10 MB
- Shipping to EU
- Shipping policy
- Ship from warehouse
States
Looks good.
Enter a valid email address.
Selection components
WebEmailWhatsApp
Feedback
Your agent is live and responding to visitors.
Training on 24 pages from your website.
Knowledge source last synced 7 days ago.
We couldn’t connect to your website. Check the URL and try again.
Changes saved×
Progress
Skeleton
OnlineTrainingErrorBetaHandoff
Card system
Metric
1,284
Conversations today
Conversation
Shipping to EU · Active
Analytics
Conversion 3.8% · +0.4%
Feature
Knowledge base sync is enabled.
ProBook Studio 16€1,299
Settings
Agent tone · Calm · helpful
Tables
| Conversation ↕ | Status | Time | Actions | |
|---|---|---|---|---|
| Product recommendation | Resolved | 2 min ago | ||
| Shipping question | Active | 5 min ago | ||
| Loading rows… | ||||
Dialogs & overlays
Use modals for focused tasks, confirmations for irreversible actions, and drawers for detail without leaving context.
Connect your website
ModalAdd the Amevia snippet to start helping visitors on your site.
Delete conversation?
ConfirmThis removes “Shipping to EU” from your dashboard. This can’t be undone.
Conversation details
Active · 5 min ago
Visitor asked about EU shipping. Agent recommended Standard (3–5 days) and offered handoff.
Loading states
Spinner / button
Progress
Indeterminate
Skeleton
Loading dashboard…
Empty states
No conversations yet
Once visitors start chatting, they will appear here.
No website connected
Connect a site to begin building your Amevia agent.
No products found
Import a catalogue or sync your store to enable recommendations.
No search results
Try a different query or clear filters to broaden results.
No analytics yet
Metrics appear after your agent starts handling conversations.
No integrations
Connect tools to sync leads, actions and workflows.
Metrics & charts
Visitors
12.4k
+8%
Conversations
1,284
+12%
Recommendations
862
+5%
Products
318
+2%
Leads
326
+9%
Actions
741
+11%
Conversion
3.8%
+0.4%
Line
Area
Bar
Pie
ResolvedActiveHandoff
Sparkline
Tooltip: Conversations · Today 1,284
Donut
ConversationsLeadsOther
Usage: light grids, restrained legends, tooltips under 80 characters. Prefer area/line for trends; bars for comparisons; donut/pie for composition.
Icon buttons, spacing, radius & shadows
Spacing
4
8
12
16
20
24
32
48
64
Radius
4
8
12
16
20
24
Pill
Shadows
None
Small
Medium
Large
Overlay
Component states
| State | Guidance |
|---|---|
| Default | Follow approved variant styles; keep motion under 250ms. |
| Hover | Follow approved variant styles; keep motion under 250ms. |
| Pressed | Follow approved variant styles; keep motion under 250ms. |
| Focused | Visible focus ring, never remove outline without replacement. |
| Active | Follow approved variant styles; keep motion under 250ms. |
| Disabled | Reduce opacity and remove pointer events. |
| Loading | Preserve width; announce with aria-busy. |
| Success | Confirm completion with short feedback. |
| Error | Pair color with text — never color alone. |
Responsive frames
Desktop
Stack forms, keep primary CTA reachable, prefer 44px targets on mobile.
Tablet
Stack forms, keep primary CTA reachable, prefer 44px targets on mobile.
Mobile
Stack forms, keep primary CTA reachable, prefer 44px targets on mobile.
Accessibility
- Keyboard: Tab, Enter/Space, Escape closes dialogs
- Focus rings use --focus-ring on all interactive controls
- ARIA: roles for tabs, dialogs, switches, busy buttons
- Touch targets: minimum 44×44px for primary actions
- Contrast: body text 4.5:1, large text and UI 3:1
- Errors: text + aria-invalid + describedby
Chat widget
The Amevia widget turns website conversations into useful outcomes. It helps visitors find answers, discover products, complete actions and reach a human when needed — without interrupting the website experience.
A · Experience overview
Principles and live product
Helpful
Every response should move the visitor toward an answer or next step.
Integrated
The widget should feel native to the website, not layered on top of it.
Trustworthy
The agent should communicate status, uncertainty and human handoff clearly.
RecommendedPreferred default pattern
ProductionAvailable and supported
BetaAvailable but evolving
ConceptDesign reference only
FutureNot yet implemented
Interactive Amevia widget
Explore the complete visitor experience from welcome to answer, action and human handoff.
Status: Production · Recommended preset: Standard · Bottom right · Auto theme
B · Core experience patterns
Approved visitor experiences
Collapsed launcher
Desktop default is icon + label. Mobile default is icon only. Keep 12–16 px safe margins. Avoid bouncing and repeated pulses.
Icon only
Mobile defaultCircular launcher with the Amevia mark for compact viewports.
Icon + label
Desktop default“Ask Amevia” for stronger discoverability on desktop.
Proactive message
OptionalOne appearance per session. Include a dismiss control.
Need help finding something?
Notification
ContextualSubtle unread indicator — no aggressive pulsing.
Online state
OptionalSmall status indicator on the launcher.
One-time reveal
Recommended motionApproved Ribbon Sweep on first appearance only.
Launcher appearance
Approved launcher styles
Use the launcher treatment that provides the clearest contrast and best fit for the host website while preserving the Amevia mark and interaction behavior.
Desktop default: Icon + label · Brand gradient
Mobile default: Icon only · Brand gradient
Light enterprise interface: Icon + label · Dark
Dark interface: Icon + label · Light
Minimal placement: Outline
Customer-branded deployment: Customer color container + approved Amevia symbol
Icon-only styles
Brand gradient
RecommendedGeneral marketing sites, Amevia-owned surfaces, light neutral pages, launches.
Dark
RecommendedLight websites, enterprise dashboards, documentation, restrained product UI.
Light
RecommendedDark websites, black or navy navigation, dark dashboards.
Outline
ProductionMinimal interfaces and low-priority placement where the launcher should stay quiet.
Transparent / surface-aware
ConceptOnly on stable solid surfaces with sufficient contrast — never over busy photos.
Icon + label styles
Brand gradient
Dark
Light
Outline
Customer brand color
Illustrative customer-brand examples — not part of the Amevia core palette. Only the container color changes; the Amevia symbol stays official. Text color is selected for contrast.
Status: Optional — controlled customer-container color only
Blue
Green
Orange
Purple
Interaction states
Default
Hover
Pressed
Focus
Unread
Online
Hover lifts 1 px with a stronger shadow. Pressed returns to rest. Focus uses the approved focus ring. No bounce, neon bloom or continuous pulse.
Contrast guidance
| Host background | Approved treatments |
|---|---|
| Light background | Gradient · Dark · Outline dark |
| Dark background | Light · Gradient · Outline light |
| Busy background | Solid backing surface — avoid transparent |
| Brand-colored background | Choose light or dark by measured contrast |
Require AA contrast for labels, a visible icon, a visible focus ring, and distinguishable unread/online indicators.
Size & spacing
- Icon only · Small: 44 px
- Icon only · Default: 52 px
- Icon only · Large: 60 px
- Icon + label height: 48–56 px
- Label padding / gap / icon: 16–20 px · 8–10 px · 24–28 px
Softly rounded / pill for labels; circular for icon-only. Never larger than the site’s primary CTA.
Recommended labels
- Ask Amevia
Contextual
- Need help?
- Chat with Amevia
- Find an answer
- Get support
Website-branded
- Ask our assistant
- Product assistant
- Support assistant
Avoid
- AI Bot
- Magic AI
- Superhuman assistant
- Chat now!!!
- Talk to robot
- Generic “Chat” when stronger context is available
Label usage
- Desktop default: Ask Amevia
- Mobile: Icon only
- Support-heavy pages: Get support
- Product discovery pages: Find a product
Contextual label pattern: start with “Ask Amevia”, change once per session to a contextual prompt such as “Need help finding something?”, then return to default after dismiss or interaction. No rapid cycling — separate from the proactive-message bubble.
Do
- Choose the variant based on host background
- Preserve the Amevia mark
- Maintain safe margins
- Keep labels concise
- Use one-time reveal motion
- Ensure accessible contrast
Don’t
- Replace the Amevia mark with a generic chat icon
- Use neon or rainbow backgrounds
- Create a fake 3D launcher
- Pulse continuously
- Stretch the icon
- Use low-contrast labels
- Place a transparent launcher over a busy image
- Make the launcher larger than the site’s primary CTA
Welcome experience
Match greeting and actions to the website type. Keep composer labels in the same language as the conversation.
Status: Production patterns
General website
E-commerce
Services
Support
Multilingual
Detected language: Romanian
Conversation, products & support
Compact production patterns. Product cards are demonstrative placeholders.
Product discovery
One product card and two clear next actions.
I need a laptop for design work.
Here are options that balance performance and portability.
ProBook Studio 16
16" · 32 GB
€1,299
In stock
Support with source
Direct answer, quiet source, recovery actions.
Typing & progress
Checking available information…
Finding relevant products…
Timing guidance
| Delay | Guidance |
|---|---|
| Under 600 ms | Respond directly |
| 600 ms–2 s | Subtle typing indicator |
| Over 2 s | Specific progress text |
| Over 8 s | Explain delay and offer cancel where appropriate |
Lead capture & confirmations
Use “Send request”, never “Submit”.
Compact lead form
Consent only when legally required.
Added to cart
ConceptRequest sent
ProductionBooking confirmed
FutureHandoff requested
BetaHandoff, offline & recovery
Low-confidence
Visitor-requested
Live human available
Human unavailable
Queue
Only show queue estimates when real data exists.
C · Responsive and visual system
Appearance, anatomy and motion
Light widget
Dark widget
Mobile bottom sheet
Recommended: bottom sheet or full-screen conversation depending on viewport height.
Anatomy & sizes
123456789
10 · Launcher sits outside the panel.
- 1Header — Brand or website-branded agent title
- 2Status — Online, offline or human role
- 3Conversation viewport — Scrollable message log
- 4Message — Visitor, agent, human or system
- 5Product card — Discovery and transactional actions
- 6Suggested actions — Reply, navigation or transactional
- 7Composer — Input with accessible send control
- 8Send button — Minimum 44×44 px touch target
- 9Footer attribution — Powered by Amevia badge
- 10Launcher — Icon or icon + label outside the panel
Size specifications
- Desktop compact: 340–360 × ~560 px
- Desktop standard: 380–420 × 560–680 px
- Desktop large: 440–480 × ~680 px
- Mobile: Full width minus safe margins, or full-screen
- Launcher: 48–56 px icon · 12–16 px page margin
Motion
| Pattern | Duration | Motion | Reduced |
|---|---|---|---|
| Launcher reveal | Under 800 ms | One-time fade/sweep | Static |
| Widget opening | 180–240 ms | Fade + scale | Instant or fade |
| Message entrance | 140–200 ms | Fade + translate | Instant |
| Typing | Continuous | Subtle opacity dots | Static text |
Full motion system: View Motion & Effects
State model
Conversations branch — they are not a single linear path.
Closed
→ Opening → Welcome → Active
Active
→ Typing→ Searching→ Waiting for action→ Lead capture→ Human requested→ Error→ Offline→ Completed
Human requested
→ Human active → Completed
Error
→ Retry → Active→ Handoff
Offline
→ Leave message → Completed
D · Governance and implementation
Accessibility, privacy and events
Accessibility
Keyboard
- Tab through controls
- Enter/Space activate
- Escape closes the widget
Focus
- Visible focus rings
- Focus returns to launcher after closing
Live regions
- Announce new agent messages
- Announce status changes
Contrast & touch
- Body text 4.5:1
- UI chrome 3:1
- Minimum 44×44 px targets
Validation & motion
- Errors use text + aria-invalid
- Reduced motion: instant open/close
Privacy & consent
Sensitive information
- Warn against passwords and payment details contextually
Consent
- Show lead consent when legally required
Transcript & deletion
- Privacy and transcript controls in overflow
- Delete conversation when plan supports it
Please avoid sharing passwords, payment details or other sensitive information.
Analytics events
Never send message content or sensitive information in analytics payloads.
| Event | Status | Trigger | Payload guidance |
|---|---|---|---|
widget_opened | Planned | Launcher opens | No message content |
message_sent | Planned | Visitor sends a message | Metadata only |
suggestion_clicked | Planned | Suggested action clicked | Action ID, not message text |
lead_submitted | Planned | Lead form completed | Consent-safe fields only |
handoff_requested | Planned | Human support requested | No sensitive transcript data |
conversation_completed | Planned | Conversation ends | Outcome metadata only |
Applications
The Amevia identity adapts across websites, product interfaces, social media, presentations, integrations and partner environments while preserving a consistent core system.
These examples demonstrate approved brand applications, not fixed product layouts.
ApprovedReady for production — downloadable or maintained assets
TemplateReusable approved pattern for designers and partners
ConceptVisual direction only — not a shipping product surface
FutureNot yet available
Website homepage
Featured product marketing surface — brand-first hero with clear CTAs.
Theme
Viewport
Your website’s AI workforce.
Engage visitors, answer questions, automate tasks and take action 24/7.
Start freeBook a demo
A · Digital product
Product interfaces
Homepage, dashboard, docs, chat and onboarding surfaces.
Dashboard
Authenticated product overview — representative, not a full app.
Theme
OverviewAgent online
Conversations
47
Leads
12
Pages indexed
24
Resolution rate
89%
Recent conversations
Pricing question · 2m
Laptop recommendation · 8m
Handoff to support · 14m
Activity
Documentation header
Contextual product lockup — not a separate master logo.
Theme
Amevia Documentation
Docs / Getting started
Install the chat widget
Add Amevia to your site with a single script tag.
Chat widget
Visitor-facing brand surface. Full system lives in the Chat widget chapter.
Login / onboarding
First authenticated moment — keep brand calm and trustworthy.
Email
Password
ContinueB · Marketing and social
Social and campaigns
Avatars, posts, Open Graph and launch visuals.
Social profile image
Symbol only — no wordmark or descriptor at avatar sizes.
Background
- Keep the symbol inside the central 70–76%
- No wordmark · no descriptor
- Avoid detailed glow at very small sizes
Social post system
Three approved templates across four platform formats.
Template
Format
Open Graph image
1200×630 share cards with safe title area.
Page type
Campaign banner
Wide social / ads banner.
Product launch visual
Launch announcement direction.
Launch with clarity — one claim, one CTA.
C · Communication and documents
Email, print and presentations
Signatures, cards, decks and report covers.
Email signature
Compact, accessible, dark-mode safe — no banners or animated logos.
Preview
Thanks for the intro — looking forward to the call.
Text fallback: Alex Morgan · Product Lead, Amevia · getamevia.com
Business card
Premium print identity — restrained, modern, production-minded.
Fictional example contact
Theme
Region
Dark front + dark back (recommended)
Front
Back
Recommended working specifications
Until printer-ready files are finalized.
- Finished size
- 85×55 mm
- Bleed
- 3 mm
- Safe area
- Minimum 4–5 mm
- Color
- CMYK · proof violet / blue / cyan carefully
- Resolution
- Raster effects 300 DPI minimum
- Files
- Print PDF · SVG master · outlined fonts
Do
- Maintain clear space around the logo
- Keep contact details concise
- Preserve strong contrast
- Proof gradient colors before printing
- Use official logo assets
Don’t
- Stretch the logo
- Use strong neon glows
- Place text too close to trim
- Use tiny contact text
- Add social icon clusters
- Ship RGB-only files for final print
Presentation system
16:9 deck templates — cover, divider, content and closing.
Slide
Brand Overview
July 2026 · Brand team
PDF report cover
Quarterly product report
Q2 2026D · Integrations and partner surfaces
Attribution and marketplaces
Powered-by badges, listings and embedded footers.
Powered by Amevia
Secondary attribution — never stretch or alter the symbol.
Theme
Icon + textPowered by Amevia
Powered by AmeviaCompactPowered by Amevia
Powered by AmeviaText-onlyPowered by Amevia
Linked badge
Chat-widget footerPowered by Amevia
Powered by AmeviaPartner footerPowered by Amevia
Integration marketplace
Listings are demonstrative — statuses reflect shipping reality.
Theme
Amevia for WordPress
Communication · WordPress 6.0+
Add an intelligent website agent to your WordPress site.
Amevia for Shopify
Commerce · Shopify Online Store 2.0
Guide shoppers and capture product intent in checkout journeys.
Amevia for Webflow
CMS · Webflow sites
Embed an Amevia agent on Webflow marketing sites.
Amevia for WooCommerce
Commerce · WooCommerce 8+
Recommend products and resolve order questions on Woo stores.
Custom API
Developer · REST / webhooks
Connect Amevia to your stack with the developer API.
Partner footer
© Partner CoPowered by Amevia
Powered by AmeviaEmbedded widget attribution
E · Dioartis ecosystem
Amevia within Dioartis
Product directory, attribution and parent-company hierarchy.
Product card on Dioartis.com
Amevia remains the product brand; Dioartis is quiet parent attribution.
Product
AI agents for websites.
A product by
Product detail header
Equal or larger Amevia presence beside Dioartis — never a hybrid mark.
A product by
Powered by Dioartis lockup
Use “A product by Dioartis” — do not merge names into one wordmark.
A product by
A product by
Accessibility
Accessibility is part of the Amevia product, not an afterthought. Every interaction should be usable with keyboard, screen readers, reduced motion and high-contrast settings.
A · Foundation
Why accessibility matters
Build once for every visitor — keyboard, assistive tech, contrast and motion preferences included.
Inclusive
Everyone should be able to use the product.
Compliant
Designed to meet WCAG 2.1 AA.
Practical
Accessibility improves usability for every visitor.
B · Core patterns
How accessibility looks in Amevia
Illustrated standards for contrast, focus, keyboard, motion, touch and semantics.
Color contrast
Body text 4.5:1 · large text and UI 3:1
Accessible text✓ Pass
Low contrast example✗ Fail
Focus states
2px ring with offset on interactive controls
Keyboard outline via :focus-visible
Keyboard navigation
Chat widget tab order
Tab
↓Navigation
↓Widget
↓Composer
↓Send
↓Launcher
Esc closes the widget · Shift+Tab reverses order
Motion
Honor prefers-reduced-motion
Default animation
Reduced motion
Touch targets
Minimum 44×44 px
32
✗44
✓56
✓Screen readers
Semantic hierarchy over div soup
<header>
<nav>
<main>
<section>
<button aria-label>
<footer>C · Implementation checklist
Ship-ready accessibility checks
Keyboard
- Tab navigation
- Shift+Tab
- Enter
- Space
- Escape
- Arrow keys where appropriate
Screen Reader
- aria-label
- role
- live regions
- alt text
- semantic HTML
Visual
- 4.5:1 contrast
- focus visible
- scalable text
- responsive zoom
Motion
- prefers-reduced-motion
- animations disabled
- no flashing
Forms
- labels
- errors
- helper text
- validation
- autocomplete
D · Examples
Good vs bad patterns
Side-by-side comparisons for common product surfaces.
Buttons
GoodNamed, 44px+ target, clear focus
BadIcon-only, tiny, no name
Forms
GoodVisible label + helper
BadPlaceholder-only label
Error state
GoodEnter a valid email address
BadRed border only — no message
Modal
Good
Confirm handoff
A teammate will join this chat.
Bad
Dialog
No title association, no Esc, focus escapes.
Chat widget
Good
Amevia · Online
Live region announces typing and replies. Esc closes.
Bad
Chat
Silent updates · trapped focus · no labels
E · Environment testing
Theme, zoom and devices
Theme
Same actions across themes — contrast and focus must remain clear.
Zoom
Layout stays usable
Content reflows without clipping critical actions at 200% zoom.
Viewport
Desktop still needs visible focus for keyboard users.
F · Screen reader flow
Live region announcements
Chat updates must be polite and timely — never silent.
I need a laptop for design work.
↓
aria-live polite
Assistant is typing↓
Assistant replied
Here are options that balance performance and portability.G · Scorecard
Accessibility readiness
WCAG AAReady
KeyboardReady
ContrastReady
MotionReady
FormsReady
ChatReady
PrintReady
H · Developers
Implementation notes
Common attributes and APIs
role="dialog"Modals and chat panels that trap focus.aria-modal="true"Background content is inert while open.aria-live="polite"Typing and reply announcements in chat.aria-labelIcon-only controls need an accessible name.prefers-reduced-motionDisable non-essential animation.:focus-visibleShow rings for keyboard, not every click.Downloads
Official brand assets for marketing, product, and partner use. Search, filter and download from the Amevia Brand Asset Center.
27Assets
4Logo variants
9Documentation
4Dev resources
Jul 2026Last update
v1.2.0Brand version
27 assets · 9 docs
A · Assets
Brand assets
Preview, download or copy paths for official files.
LatestRecommended
Logo package
Complete approved logo kit — SVG, PNG, monochrome, favicon and lockups.
amevia-logo-kit.zip
RecommendedStable
Primary horizontal logo
Default lockup for headers, light UI and marketing pages.
amevia-logo-horizontal.svg
Stable
Dark background logo
Horizontal lockup for navy heroes and dark navigation.
amevia-logo-horizontal-dark.svg
Stable
Stacked logo
Vertical lockup for square formats and compact placements.
amevia-logo-stacked.svg
Stable
Horizontal + descriptor
Horizontal logo with product descriptor line.
amevia-logo-horizontal-tagline.svg
RecommendedStable
Gradient icon
Primary Amevia symbol with brand gradient fill.
amevia-icon-gradient.svg
Stable
Monochrome icon (black)
Single-color symbol for light backgrounds and print.
amevia-icon-black.svg
RecommendedStable
Favicon SVG
Solid gradient tile favicon for browser tabs — no transparent gaps.
favicon.svg
RecommendedMarketing
Powered by badge
Partner attribution badge for light backgrounds.
powered-by-amevia.svg
MarketingStable
Powered by badge (dark)
Partner attribution badge for dark backgrounds.
powered-by-amevia-dark.svg
MarketingStable
Social banner
Wide campaign banner for social headers and ads.
amevia-social-banner.svg
MarketingStable
Social avatar
Square profile mark for social channels.
amevia-social-avatar.svg
Stable
Logo system preview
Interactive HTML preview of the logo system.
amevia-logo-system.html
DeveloperRecommended
Color tokens (CSS)
CSS custom properties for the Amevia palette.
amevia-colors.css
DeveloperStable
Color tokens (SCSS)
SCSS variables for Sass-based codebases.
amevia-colors.scss
DeveloperStable
Color tokens (Tailwind)
Tailwind theme snippet for Amevia colors.
amevia-colors.tailwind.js
RecommendedStable
Voice and tone guide
Writing principles for product and marketing copy.
voice-and-tone.md
MarketingRecommended
Messaging toolkit
Packaged messaging references for go-to-market teams.
amevia-messaging-toolkit.zip
B · Documentation
Guides and references
Markdown sources of truth for brand, product and writing.
Brand book index
Entry point to the full brand documentation set.
2 minMarkdown
Brand strategy
Purpose, positioning and strategic foundations.
9 minMarkdown
Voice & Tone
Writing principles for clear, confident Amevia copy.
5 minMarkdown
Messaging
Narrative pillars, elevators and proof points.
2 minMarkdown
Logo guidelines
Clear space, minimum sizes and incorrect usage.
4 minMarkdown
Color and type system
Palette, contrast and typography tokens.
6 minMarkdown
UI guidelines
Component and interface patterns for product UI.
5 minMarkdown
Accessibility
WCAG AA practices across product and brand surfaces.
5 minMarkdown
Brand motion
Motion language, timing curves and reduced motion.
4 minMarkdown
C · Developer resources
Tokens and tooling
Ship with official token files. Future packages stay marked until published.
CSS variables
Custom properties for color and brand tokens.
Tailwind config
Theme snippet for Tailwind-based products.
JSON tokens
Portable token source for design tooling.
SCSS tokens
Sass variables mirroring the CSS token set.
Figma variables
Shared Figma library for design teams.
Coming soonSVG sprite
Combined symbol sprite for product icons.
Coming soonReact icons
Typed React components for brand and UI icons.
Coming soonNPM package
Published package for tokens and icon components.
Coming soonD · API / CDN
Integrations
Reserved for official distribution channels. Only live links are enabled.
Official CDNComing soon
GitHubComing soon
FigmaComing soon
NPMComing soon
REST APIComing soon
Governance
Amevia’s identity should evolve deliberately. New assets, product names, visual treatments and partner applications must extend the existing system rather than create parallel versions of the brand.
One brand system. One approved source of truth. Deliberate evolution.
A · Principles
Governance principles
Consistency
Use approved assets, tokens and messaging across every touchpoint.
Clarity
Every addition must have a defined purpose, owner and usage context.
Compatibility
New work must remain compatible with existing product, marketing and accessibility standards.
Traceability
Significant brand changes must be versioned and documented.
B · Source of truth
Official source of truth
Use these locations only. Parallel copies become unofficial the moment they diverge.
Source status: Maintained
- Brand assets
public/brand/ - Design tokens
styles/tokens.css - Documentation
Brand Book · /docs/ - Messaging & voice
public/docs/ · messaging & voice guides - Components
Production design-system components
- Do not recreate logos manually.
- Do not copy assets from screenshots.
- Do not maintain parallel token files.
- Do not duplicate messaging in disconnected documents.
- Do not use local modified copies as official assets.
C · Ownership
Ownership and responsibility
Roles only — decisions are owned by function, not by informal preference.
Brand owner
Dioartis- Final brand decisions
- Naming
- Logo and visual identity
- Public positioning
Design-system owner
Dioartis Design System- Tokens
- Components
- Accessibility
- Visual implementation
Product owner
Amevia product- Product-specific applications
- Feature naming
- UI consistency
Content owner
Amevia content- Messaging
- Voice and tone
- Terminology
- Localization
Engineering owner
Amevia engineering- Implementation quality
- Asset integrity
- Versioned delivery
- Build compatibility
D · Approval
Change approval process
Propose
Describe the problem, intended use and affected surfaces.
Review
Check brand fit, accessibility, technical impact and duplication.
Validate
Test in real product and marketing contexts.
Approve
Assign an owner, version and implementation status.
Publish
Update assets, tokens, documentation and changelog together.
No significant brand change should be published by updating only the visual file. The related documentation and source assets must also be updated.
E · Classification
Change classification
Patch
Minor correction that does not change brand meaning.
- Metadata correction
- Export optimization
- Accessibility fix
- File-path correction
Minor
New approved variant or component that extends the existing system.
- New social template
- New launcher treatment
- Additional icon
- New approved language
Major
Change affecting the core identity or positioning. Requires broader review and a new major brand version.
- Logo geometry
- Primary colors
- Typography
- Product name
- Core tagline
- Sub-brand architecture
F · Versioning
Versioning
Semantic-style brand versions: Major.Minor.Patch
Brand Bookv1.2.0
Asset packagev1.2.0
Last updatedJul 2026
SchemeMajor.Minor.Patch
- MajorCore identity or positioning change
- MinorNew approved assets or substantial system extension
- PatchCorrections, optimization and documentation fixes
Recent changes
| Version | Date | Change | Impact |
|---|---|---|---|
| 1.2.0 | Jul 2026 | Brand Asset Center, Accessibility design system, and Governance framework added to the Brand Book. | Minor |
| 1.0.0 | Jul 2026 | Initial approved Amevia brand system. | Major |
Full changelog is maintained in this Brand Book. Detailed release history begins with the initial approved system.
G · Colors
New colors
Every proposal must include
- Name
- HEX
- RGB
- HSL
- Optional CMYK working value
- Semantic role
- Light-mode usage
- Dark-mode usage
- Contrast verification
- Token name
- Examples in context
Approval requirements
- Must solve a real design-system need
- Must not duplicate an existing color
- Must pass accessibility testing
- Must be added to styles/tokens.css
- Must be documented in Color
- Must include migration guidance when replacing another token
Do not allow direct component-specific color additions without semantic token mapping.
H · Icons
New icons
Standards
- 24 px base grid
- 1.75 px stroke where applicable
- Rounded line caps and joins
- Outlined default style
- Optical alignment
- currentColor support
- Accessible naming
- SVG optimization
- No embedded raster images
- No unrelated visual style
Required deliverables
- SVG source
- Optimized SVG
- Title / name
- Usage description
- Category
- Light and dark tests
- 16, 20 and 24 px legibility test
I · Components
New components
Create only when
- An existing pattern cannot solve the use case
- The need appears across multiple surfaces
- Interaction behavior is defined
- All states are documented
- Accessibility is validated
- Responsive behavior is tested
- Design tokens are reused
- Production status is assigned
Avoid creating one-off Brand Book-only components that do not map to real product needs.
Required states where applicable
DefaultHoverFocusActiveDisabledLoadingErrorSuccessEmpty
J · Product architecture
Product architecture
Core product remains Amevia. Descriptors are examples until formally launched.
Status: Naming examples only
Core product
Amevia
Potential future descriptors
Amevia AgentAmevia StudioAmevia AnalyticsAmevia IntegrationsAmevia APIAmevia Commerce
Rules
- No product name is active until formally approved and launched.
- Use “Amevia + descriptor”.
- Descriptors should be clear and functional.
- Avoid invented words that reduce clarity.
- Do not create separate logos automatically.
- Use the Amevia master brand with a contextual descriptor.
- Preserve the core Amevia wordmark.
- Avoid combining product names into one word.
Preferred
Amevia Analytics
Avoid
AmeviaAnalyticsAmevia AI Analytics ProAmeviaX
K · Lockups
Product lockups
Naming architecture examples — not official logo exports.
Amevia
AnalyticsStacked descriptor example
Amevia Analytics
Inline descriptor example
- Master Amevia logo remains unchanged
- Descriptor uses approved typography
- Descriptor is visually secondary
- No separate symbol
- No separate gradient
- No independent color system without approval
L · Partners
Partner co-branding
A. Powered by AmeviaB. Partner logo + Amevia logoC. Integrated with AmeviaD. Amevia integration listing
- Amevia mark must remain unmodified
- Logos need clear separation
- Partner logo may be equal or smaller depending on context
- No shared or blended symbol
- No merged wordmark
- No recoloring the Amevia mark
- No dividing line through either logo
- No implied partnership beyond the actual relationship
Recommended spacing: at least one Amevia symbol-width between independent logos (clear-space rule).
Do
Partner|
Don’t
PartnerAmevia hybrid
Do
Don’t
Amevia-powered-by-Partner
M · Parent brand
Amevia and Dioartis
Approved statements
- A product by Dioartis
- Amevia is a product of Dioartis Grup SRL.
Use cases
- Brand Book
- Dioartis product directory
- Legal pages
- Corporate presentations
- Press materials
- Selected partner documents
Rules
- Amevia remains the primary product brand
- Dioartis attribution is secondary
- Do not merge the two logos
- Do not create “Dioartis Amevia” as a new product name
- Use the official Dioartis logo asset
- Maintain clear space
- Parent attribution may be omitted from compact customer-facing UI when unnecessary
A product by
Approved lockup preview — Amevia remains primary; Dioartis is secondary.N · Classification
Public vs internal assets
- Approved logos
- Public brand guidelines
- Social templates
- Powered by Amevia badge
- Approved product descriptions
- Partner decks
- Co-branding templates
- Integration assets
- Sales collateral
- Editable source files
- Unreleased product names
- Experimental colors
- Concept designs
- Roadmap assets
- Internal implementation notes
Do not expose internal source files through the public Downloads section unless intended.
O · Deprecation
Deprecation policy
ConceptBetaProductionDeprecatedArchived
Not every asset must pass through every stage.
- Mark it Deprecated
- Document the replacement
- Preserve it temporarily where required
- Add a removal date or target version
- Update all official templates
- Avoid deleting files silently
- Provide migration notes for developers
P · Quality
Pre-publication checklist
- Correct official logo source
- Approved colors and tokens
- Typography matches the system
- Sufficient contrast
- Keyboard and screen-reader behavior where interactive
- Responsive behavior
- Light and dark testing
- Print testing where applicable
- Correct naming
- Accurate product status
- Documentation updated
- Downloads updated
- Version updated
- Changelog updated
- No unsupported product claims
- No third-party rights issues
Q · Requests
Request a brand change
No public intake form is published yet. Use this template when opening an internal request.
- Proposed change
- Reason
- Affected surfaces
- Mockup or example
- Accessibility impact
- Technical impact
- Launch date
- Owner
R · Cadence
Recommended governance cadence
Guidance only — not a fixed corporate process unless formally adopted.
- QuarterlyAssets, broken links and documentation
- Before major launchMessaging, product naming and applications
- AnnuallyFull brand-system review
- ImmediatelyAccessibility, legal or security corrections
S · Practice
Governance Do / Don’t
Do
- Extend the existing system
- Document decisions
- Reuse tokens
- Validate accessibility
- Version significant changes
- Update source and documentation together
Don’t
- Recreate assets from screenshots
- Publish unapproved product names
- Add isolated hard-coded colors
- Modify logo proportions
- Ship undocumented variants
- Mark concepts as production
- Create hybrid partner logos
Amevia
Your website’s AI workforce.
Built to help every visitor find answers, discover what matters and take useful action.
Brand Book · Version 1.2.0
Last updated Jul 2026
Maintained by Dioartis
A product by