Sovereign cloud.Software that's alive.

Top line, locked. Sovereign cloud. Software that's alive.

Five public pillars, in this order. On-demand · Tamperproof · Always-on · Fluid · Yours. The italic on Yours is locked. These pillars run on the homepage strap and on every public-facing surface (banners, VC backgrounds, signatures, decks).

Long form: ICP is a sovereign cloud where the software itself is alive. Apps are generated on demand through AI chat and keep extending themselves over time with new natural-language functionality, while the network underneath runs them tamperproof, always-on, and under your control. It runs the whole app on the network itself, the frontend, the data, and the backend logic.

• On-demand. Apps, SaaS, and websites are generated through AI chat at the speed of conversation. No team to provision, no infrastructure to set up first.
• Tamperproof. Security is a property of the network, not a team. Tamperproof execution, replication, and code integrity are enforced by math across the nodes. No security team, no sysadmin, no compliance officer needed for what the network already enforces.
• Always-on. Nodes are distributed across independent locations, so an app keeps serving users even if a whole data centre goes down. No patch windows, no maintenance pages.
• Fluid. Software is not a static binary. AI can see the data inside the running app and extend its functionality on the fly through natural-language interfaces. Same app, new capability, no redeploy.
• Yours. An app deployed to ICP is not locked to a cloud vendor. Pick the hardware, the operators, and the jurisdiction. Move between providers, or off them entirely, without downtime.

Out of scope. Products with their own brand identity, like OISY and Caffeine, are not covered here. They have their own voice and visual systems.

The canonical strap above is the master positioning and ships on every off-homepage surface: decks, social banners, video conference backgrounds, email signatures, deck covers, investor and press pages, this guide. The internetcomputer.org homepage runs a product-led variant of the H1 that names the artifact ICP runs, rather than the metaphor that describes it. The two coexist on purpose: alive. describes what the network is, AIware describes what runs on it.

Eyebrow. § Internet Computer Protocol (ICP) · The internet overlay for AIware

Hero H1, line one (static). Sovereign cloud.

Hero H1, line two (rotation). A two-state rotation between Runs AIware. and Tamperproof, always-on. Both phrases are italic-rust in full. This is a controlled exception to the one-italic-word rule and is scoped to the homepage hero only. Both states are baked into the DOM (one in an invisible measurement layer for stable layout, one in an absolutely positioned live layer) with aria-live="polite".

Sub-strap. Create custom AIware apps and SaaS on-demand, which have fluid functionality. Italic-rust on fluid functionality only.

Where this variant is allowed. internetcomputer.org homepage and product pages on the same domain that talk about what ICP runs. Nowhere else. Off-homepage surfaces continue to ship the canonical strap with italic-rust on alive., and the one-italic-word rule still applies there.

Spelling, locked. Always written AIware as one word: capital A, capital I, lowercase ware. Never AIWare, aiware, AI-ware, AIWARE, or AI ware. Treat as a proper noun.

What it means. A new category of software that AI agents generate, extend, and operate on demand. AIware apps are generated through AI chat, expose their data and logic to the agent so it can add new functionality on the fly, and run end-to-end on the Internet Computer so they stay tamperproof, always-on, and under the user's control.

Part of speech. Noun and adjective. Runs AIware (noun). AIware apps (adjective). Sophisticated AIware (noun). The same word does both jobs without modification.

Do not substitute. Do not replace AIware with AI agents, agentic apps, AI-native apps, or agent-built apps on surfaces that reference the internetcomputer.org product noun. Those phrases describe the actors or the building style; AIware is the artifact.

Relationship to the canonical strap. The canonical strap (alive.) describes what the network is. AIware names what runs on it. Both are correct, and both can appear on the same page when it serves the audience. The canonical strap stays the master line on off-homepage surfaces.

Two surface tools reduce visual monotony without resorting to boxes, shadows, or color blocks. The page background is parchment, sunk parchment is for alternating sections and sunk panels, and the grid paper is a near-invisible texture used on hero and feature surfaces.

Five raster sizes ship: 16, 32, 48, 192, 512. The 16 px tile is the only size most users ever see, so the mark is centered with comfortable padding and the gradient is allowed to soften rather than fight the pixel grid. The 192 and 512 sizes cover Android home screens and PWA install dialogs.

iOS does not auto-theme home-screen tiles, so two variants ship: a parchment fill for light wallpapers and a deep-bark fill for dark wallpapers. The Safari pinned-tab mark is a single-color silhouette which Apple recolors at runtime; the brand value is rust #a8482b, declared in the color attribute of the mask-icon link.

The brand's signature grid paper texture does not survive at sixteen pixels. Compressed into a tab-strip tile, the grid stops reading as a system gesture and starts reading as noise that fights the gradient infinity. The favicon's only job is to let the mark resolve cleanly. The grid stays where it can breathe: hero sections, banners, document headers.

One picture, used everywhere. 400 × 400 PNG, parchment fill #faf9f5, gradient infinity centered at sixty percent canvas width. The mark sits on the same parchment as the banner, so the avatar and the banner together read as a single continuous surface. No grid texture, no container, no wordmark on the avatar. The favicon section covers why the grid does not survive at small sizes; the same logic applies at sixty-four pixels in a feed.

1584 × 396 base, 4:1 aspect ratio. This is the banner behind a personal LinkedIn profile, not a company page. Upload the 6336 × 1584 variant (4x retina) so the image stays sharp on high-DPI screens; LinkedIn scales it down to the 1584 × 396 display frame. The profile-photo circle overlaps the lower-left of the banner at roughly 152 × 152 pixels, positioned about 112 pixels in from the left and 204 pixels down from the top. The mobile-safe zone is the central 1350 × 230 pixel band. Right-aligned three-line stack lives inside that central band, anchored seventy-two pixels in from the right edge. Do not reuse the company banner (6:1) on a personal profile: LinkedIn adds hard black bars top and bottom because a 6:1 image cannot fit a 4:1 frame.

4200 × 700 upload, 6:1 aspect ratio. This is the banner behind a LinkedIn company page, not a personal profile. LinkedIn renders the company-page banner at roughly 1128 × 191 in the page layout but uploading at the full 4200 × 700 keeps it sharp on retina. The company logo overlays the bottom-left of the banner as a rounded square (roughly the left twenty-two percent of the frame and the bottom sixty percent). On mobile LinkedIn crops the company banner to the central nine hundred pixels of the displayed width. Right-aligned three-line stack lives inside that mobile-safe central band, anchored one hundred and forty pixels in from the right edge. Do not reuse the personal profile banner (4:1) on a company page: it will be stretched horizontally and lose its right anchor.

1500 × 500 source, 3:1 ratio. The circular avatar overlaps the lower-left of the header at roughly 220 × 220 pixels on desktop and shifts toward bottom-center on mobile. Mobile also trims about fifty pixels off the top and fifty off the bottom of the banner, and the action button covers a 200 × 100 region in the lower-right on phones. The same right-aligned three-line stack lives in the upper-right safe band, anchored fifty pixels in from the right edge and seventy pixels down from the top.

Three lines, never four. Eyebrow, strap, pillar row. A fourth element crowds the avatar zone and breaks the central band on every device.

No logo on the banner. The avatar carries the logo. Putting the mark on the banner duplicates the brand at the same eye-line and steals space from the strap. The banner background is parchment with grid texture and a soft rust radial glow; the mark lives in the profile picture only.

Eyebrow. Inter, thirteen pixels on X, twenty-eight pixels on the 4200 × 700 LinkedIn company banner, forty-four pixels on the 6336 × 1584 LinkedIn personal banner (which renders at roughly eleven pixels in the layout). UPPERCASE, letter-spacing 0.32em. Use the product name (INTERNET COMPUTER), not the company name. The eyebrow grounds the strap in a specific surface.

Strap. Newsreader weight 380, italic-rust on the metaphor word. Seventy-six pixels on X, one hundred and sixty-eight pixels on the 4200 × 700 LinkedIn company banner, three hundred and sixty pixels on the 6336 × 1584 LinkedIn personal banner (which renders at roughly ninety pixels in the layout). Line-height 1.02 to 1.06. Two sentences, italic-rust word at the end of the second line. The current locked strap is Sovereign cloud. Software that's alive.; italic-rust on alive only. Periods are kept on banners now that the strap is built as two true sentences, which is the same rule the rest of the brand applies.

Pillar row. Newsreader weight 400, twenty-two pixels on X, fifty-two pixels on the 4200 × 700 LinkedIn company banner, one hundred and eight pixels on the 6336 × 1584 LinkedIn personal banner. Five pillars separated by middots, italic on Yours only. The current locked pillar row is On-demand · Tamperproof · Always-on · Fluid · Yours. On narrow social crops where five pillars will not fit, drop the first two and ship the compressed row: Always-on · Fluid · Yours. Never drop Yours.

Right-aligned, never centered. On the LinkedIn company banner the stack sits one hundred and forty pixels in from the right edge of the 4200 px canvas. On the LinkedIn personal banner the stack sits seventy-two pixels in from the right edge of the 1584 px canvas (two hundred and eighty-eight pixels on the 6336 px upload). On X the stack sits fifty pixels in from the right edge of the 1500 px canvas and seventy pixels down from the top. Right alignment gives the avatar its own quadrant and balances the parchment grid on the left half.

Avatar and photo safe zones, codified. On the LinkedIn company banner keep the entire bottom-left quadrant (roughly x 0 to 930, y 280 to 700 on the 4200 × 700 canvas) clear of text. On the LinkedIn personal banner keep the lower-left region clear: a 152 × 152 pixel circle at x 112 y 204 on the 1584 × 396 canvas, with a generous margin around it. On X keep the lower-left 220 × 220 region clear, plus the top and bottom fifty pixel mobile crop bands and the lower-right 200 × 100 button zone on mobile.

• No company logo on the avatar. The infinity mark is the logo at this size.
• No grid texture on the avatar or the banner. The grid is a hero device and does not survive social compression.
• No event-specific or campaign overlays on the default profile picture. Campaign avatars exist as a separate, time-boxed asset.
• No emoji in the bio, banner, or post copy. No exceptions.
• No bare "onchain" or "on-chain" in the bio, the banner, or any tagline.

One composition, two themes. Light parchment is the default and matches the brand's editorial register on every other surface. Deep bark is for low-light environments and evening calls where parchment glares. Both carry the same locked lockup in the upper band of the frame: an Inter UPPERCASE eyebrow, the strap with italic-rust on alive, and the pillar row with italic on Yours. The mark sits in the top-right corner, aligned with the eyebrow baseline. Both ship with a soft tonal glow that moves between two values already in tokens.css (--icp-bg and --icp-bg-sunk), brighter at the top where the type sits, slightly deeper toward the bottom where the speaker tiles will land. No campaign overlay, no event badge, no neutral version: the editorial lockup is the brand on a call, every call.

Speaker safe zone, never violated. Speaker tiles in Zoom, Meet, and Teams render in the lower two thirds of the virtual background. Treat the area from thirty percent canvas height down to the bottom edge as off-limits for any mark, type, or texture-heavy element. Every shipped variant has been tested by overlaying meeting-grid tile rectangles to confirm no speaker frame intersects the lockup.

Mark top-right. The gradient infinity sits in the top-right corner, aligned with the eyebrow baseline at the top. On the master 3840 × 2160 file the mark is 200 pixels wide; in the 1920 × 1080 export it scales proportionally. The mark is the quietest fixed element on the canvas, never larger than the strap. Never center the mark and never place it at the bottom where speaker tiles would cover it.

Type top-left, never center. The locked tagline sits at the top-left of the frame, anchored ninety-six pixels in from the left edge. The eyebrow sits at thirty-four pixels Inter, the strap at one hundred twenty pixels Newsreader weight 380 with italic-rust on "alive", and the pillar row at thirty-eight pixels Inter with italic on "Yours" only. The entire lockup occupies the upper twenty-five percent of the canvas. Centered text fights the speaker; bottom-anchored text gets covered by speaker tiles.

Paper grid, denser inside the speaker zone. A faint base grid of one-pixel rust lines runs across the full canvas at five percent ink on parchment and six and a half percent on bark. Inside a soft circular region centered on where the speaker sits (fifty percent canvas width, sixty percent canvas height, forty-two percent radius), a second, stronger grid layer is painted at thirteen percent fine and eighteen percent major, masked with a feathered radial that fades to zero at the edge of the circle. The math paper is most visible exactly where the speaker's shoulders would otherwise hard-cut against the parchment, giving texture to blend into. Major gridlines every fifth square (four hundred pixels) read as engineering paper, not screen graph. Webcam compression should preserve the masking gradient because the values are all within four percent of each other in the dark zone.

Rust glow under the lockup only. A soft radial of rust at eight percent ink (parchment) or fourteen percent ember (bark) sits behind the eyebrow, strap, and pillar row in the upper-left, eighteen percent canvas width by twenty-two percent height, fading to zero by forty-two percent radius. The rest of the canvas stays flat warm parchment or flat bark. No edge vignette, no full-canvas glow, no second accent. The rust under the lockup ties the type to the brand accent; everywhere else, the eye should rest on the paper.

Master resolution, 3840 × 2160. Every variant ships as a single 4K master. Zoom, Meet, and Teams downscale the file at the client side without artifacts. Recorded keynotes, hardware backdrops, and 4K streams use the file directly. Shipping one master file per variant cuts the bundle from four to two files, removes any chance of a stale 1080p export drifting from the 4K composition, and keeps the canister assets in lockstep with the SVG source.

Zoom. Settings → Background and Effects → Virtual Backgrounds → add image. Upload the 3840 × 2160 file; Zoom downscales locally. Disable mirror to keep the mark in the top-right and the type on the left.

Google Meet. Pre-call screen → effects → backgrounds → upload. Same 3840 × 2160 file. Meet auto-mirrors local preview but ships unmirrored to other participants, which is the correct behaviour.

Microsoft Teams. Pre-call → background filters → add new → upload. Same 3840 × 2160 file. Teams crops slightly more aggressively at the top, so the speaker safe zone matters most here.

Recorded keynotes. Use the 3840 × 2160 file as a static composite under a chroma-keyed speaker plate, or as the rear screen on a hardware backdrop.

• No campaign overlays, slogans, or event badges baked into the default backgrounds. Campaign backgrounds exist as separate, time-boxed assets.
• No URL or contact strip on the canvas. The brand surface is the call, not a billboard.
• No drop shadow, no gradient fill, no 3D render of the mark. The mark is the same flat gradient infinity used on the favicon and the social profile picture.
• No emoji, no exclamation marks, no "join us at" copy.
• No bare "onchain" or "on-chain" on the editorial tagline. The locked strap is the only tagline that ships on a video background.
• No mirrored variant. The mark always reads top-right when the call is sent to other participants.

Bundle ships as a single zip with the two variants at the master 3840 × 2160 resolution, two files in total. The 1080p exports are retired; the 4K masters downscale cleanly on every meeting client and remove any risk of a stale lower-res file drifting from the master composition.

Type a name, title, and organisation. The generator renders the signature live in light and dark, then copies the production HTML to the clipboard. The mark, fonts, colours, and disclaimer travel with the paste; the wrapper preview chrome is stripped before copy.

Right-sized for real inboxes. The signature is metadata, not a billboard. The shipped sizes are calibrated to sit roughly one notch above the standard 14px Gmail body text, so the signature reads as a clean closing block rather than an oversized lockup that competes with the message itself. Every measurement below is deliberate; bigger is not better.

The mark is still and small. Animated marks read as unprofessional in a business signature, and most clients (Outlook, Gmail mobile, Apple Mail in low-data mode) block animation by default anyway. Use the same gradient infinity that ships in the favicon set, rendered to a 112 × 112 PNG and displayed at 40 × 40 for crisp Retina without dominating the block. The mark embeds as a base64 data URI in the HTML so it survives image-blocking and does not depend on a hotlink.

Newsreader for the name, Inter for everything else. Name is Newsreader weight 500 at fifteen pixels, line-height 1.25, letter-spacing -0.005em. Title and organisation are Inter weight 400 at twelve pixels in --icp-fg-secondary, separated by a middot (·) with two spaces on each side. The middot replaces the pipe character. Pipes read as code; middots read as editorial.

One rust link, one secondary link. The eyebrow link row is Inter weight 500 at ten pixels, UPPERCASE, letter-spacing 0.16em. The primary link is internetcomputer.org in the rust accent. The secondary link is dfinity.org in --icp-fg-secondary. A hairline pipe in --icp-rule separates them. Skills surfaces always come first, matching the locked order on the live site (skills.internetcomputer.org → caffeine.ai → icp.ninja); since neither of those URLs sits in a personal signature, the live-site primary internetcomputer.org takes the rust accent and dfinity.org takes secondary.

Hairline rule, never a coloured bar. The horizontal hairline below the stack uses --icp-rule at 1 pixel (warm ivory #e7e3da on light, soil #2d2820 on dark). The previous template used a vertical blue bar in a non-brand colour. The hairline rule is the same separator pattern used on every brand surface; it travels with the system.

Two-sentence disclaimer ceiling. Disclaimers grow over time and end up longer than the signature itself. The shipped template caps the disclaimer at two sentences in Newsreader weight 400 at eleven pixels, line-height 1.55, in --icp-fg-secondary, with a 620-pixel max-width so it does not flow as one long line on wide screens. Anything beyond the two sentences belongs in a separate confidentiality footer at the bottom of the message thread, not in the signature itself.

Outlook-safe, table-based. The production HTML uses a <table> for layout because Outlook on Windows uses Word as its renderer and ignores flexbox, grid, and most modern CSS. Styles are inline because many clients strip <style> blocks. The mark is a base64 PNG because hotlinked images get blocked by default. Font stacks fall back from Newsreader to Georgia and from Inter to system-ui, so the signature still reads on brand even when the web fonts are not installed locally.

Gmail. Settings (gear) → See all settings → General → Signature → Create new. In the generator above, click "Copy rendered", then paste into the Gmail signature editor. The mark and inline styles travel with the paste. Save changes at the bottom of the settings page.

Apple Mail. Mail → Settings → Signatures → add a new signature, then drag and drop a temporary placeholder image. Quit Mail. In Finder, open ~/Library/Mail/V*/MailData/Signatures/ and replace the .mailsignature file contents with the output of "Copy HTML". Reopen Mail and the signature is live.

Outlook. File → Options → Mail → Signatures → New. Click "Copy rendered" and paste into the editor. Outlook strips some inline styles on paste; if the layout breaks, edit the underlying .htm file in %AppData%\Microsoft\Signatures\ and replace it with the output of "Copy HTML".

Other clients. Most modern mail clients (Superhuman, Spark, Hey) accept HTML signatures via a paste-from-browser flow. Click "Copy rendered" and paste into the client's signature editor.

• No animated mark. Ever. The infinity is still.
• No coloured separator bar. The vertical pipe in a non-brand blue is replaced with a hairline rule.
• No bold sans-serif name. Newsreader 500 carries the name in the same editorial register as the brand surfaces.
• No phone number, no street address, no "Sent from my iPhone" tail. Three lines is enough.
• No social icon strip. The eyebrow link row is the only outbound surface.
• No quote of the day, no calendar booking link in rust, no "please consider the environment before printing" line. The signature is editorial, not a billboard.

The generator is the recommended workflow. The static templates remain available for users who want a versioned copy or who edit the HTML directly: light is the default, dark is for users whose mail client renders dark mode by default.