The portal is the product.

Logos, colors, typography, and guidelines — already structured.

Every portal opens with the four modules a brand actually needs: Logos, Colors, Typography, Brand Guidelines. They're not folders to fill — they're built for the way each kind of asset is used.

Add custom modules from the brand settings panel when you need them, like Iconography, Imagery Style, or Templates. Reorder freely.

• —Logos in SVG, PNG, JPG, PDF, EPS, AI, WebP, Other
• —Colors in HEX, RGB, HSL, CMYK, Pantone, CSS variable, Tailwind token, SCSS variable
• —Typography with WOFF2, WOFF, TTF, OTF previewed live
• —Guidelines as a PDF, a Figma link, a Notion page, a Drive folder
• —Custom modules with the same logo-card shape

Folders, when folders are the right answer.

Some brand work doesn't fit a token: campaign artwork, photography, marketing decks, print-ready files. The Library section is the open shelf — nested folders, up to five levels deep.

Default folders ship ready-to-use: Web, Stock Images, Marketing, Print Media. Rename them, hide them, add your own.

• —Nested folders up to 5 levels deep
• —Default structure: Web, Stock Images, Marketing, Print Media
• —Rename, reorder, or hide any folder
• —Bulk upload into any folder

Three roles. One question: who needs in.

Owners run the portal. Editors maintain the content. Viewers download what they need. That's it. No permission matrix to memorize.

For external clients without an account, password-protected portals work the same way — one link, one password, viewer-equivalent access.

• —Per-portal members
• —Email invitations
• —Password-gated public links with brute-force protection
• —Login-gated private portals

Every download is a signed link.

When someone downloads, the portal authorizes the request, logs the event, and issues a short-lived URL tied to the file's checksum. Nothing about the file is public.

Bulk downloads are packaged into a single zip on demand and delivered the same way.

• —5-minute signed URLs by default
• —Checksum-bound caching
• —Per-folder or per-selection ZIP exports
• —Private buckets, no public reads

Built in two languages from day one.

The dashboard, the client portal, the emails, the validation messages, even the dates and numbers — everything renders in en-US or es-MX. Pick the default for each portal so anonymous visitors land in the brand's intended language.

Designed for studios that work across borders. More languages on the roadmap.

• —Full en-US and es-MX support across all surfaces
• —Per-portal default locale setting
• —Locale-aware date and number formatting
• —More languages on the roadmap Coming

A portal that feels like a private app, not a folder.

When your client opens the portal, they don't see a Drive list. They see brand modules with real specimens, copyable color values, downloadable logos in the right format, and guidelines a click away.

Cover image, brand-driven typography, the brand's own colors. Polished by default, customizable when you want to.

• —Custom cover image and portal name
• —Brand token display: colors, typography specimens
• —Format-aware logo downloads
• —Guidelines linked directly from the portal

What we're building next.

We commit to one phase at a time. Here's the next two.

• —Custom domains and white-label portals Coming
• —Workspace-level roles and member management Coming
• —Asset versioning UI Coming
• —Per-asset signed share links Coming
• —PDF and SVG inline previews Coming
• —Search across portals Coming
• —API access and webhooks Coming
• —Figma plugin for token sync Coming
• —AI-assisted tagging and color extraction Coming