Cortlet iconCortlet
Cortlet badges

Say how you
use Cortlet.

Use official Cortlet badges to describe integrations, infrastructure, and products accurately without implying endorsement or partnership.

Badge meanings

Three badges.
Three relationships.

Pick the badge based on what Cortlet actually does for your product.

01

Built with Cortlet

Use when Cortlet is one of the technologies used to build the product.

02

Powered by Cortlet

Use when Cortlet provides meaningful underlying functionality or infrastructure.

03

Works with Cortlet

Use when your product integrates with or is compatible with Cortlet.

Example 01 // Website

Badge usage

Use the badge that matches the relationship.

Cortlet badges can be used on websites, documentation, README files, product pages, and other places where you want to describe how your product relates to Cortlet.

Use Built with Cortlet when Cortlet is part of how your product was built.

Use Powered by Cortlet when Cortlet provides underlying infrastructure or functionality.

Use Works with Cortlet when your product integrates or is compatible with Cortlet.

example.dev
ACME

Fictional developer product

Realtime infrastructure without the complexity.

ACME is a fictional product used to demonstrate correct Cortlet badge placement in context.

Built with Cortlet

Infrastructure

WebSocket gateway

Persistent WebSocket connections handled by Cortlet.

Powered by Cortlet
© ACME // FICTIONAL EXAMPLEWorks with Cortlet
Built with Cortlet

Built with Cortlet

Use when Cortlet is part of the technology used to build the product.

Powered by Cortlet

Powered by Cortlet

Use when Cortlet provides meaningful underlying infrastructure or functionality.

Works with Cortlet

Works with Cortlet

Use when the product integrates with or is compatible with Cortlet.

01

Keep it secondary

Your own product or organization should remain the primary identity.

02

Use accurate wording

Choose the badge that truthfully describes the relationship with Cortlet.

03

Do not modify

Use the official badge artwork without stretching, recoloring, or rebuilding it.

Example 02 // README

README usage

Show the relationship clearly.

Cortlet badges can appear in project README files, documentation, repositories, and developer pages when the wording accurately reflects how the project relates to Cortlet.

Place badges near the project introduction or technology section.

Keep the project's own name and identity primary.

Use only the badge whose wording accurately describes the relationship.

README.md
fictional repository

realtime-kit

A fictional toolkit for building realtime application features with a simple serverless backend.

Built with CortletMITTypeScript

About

realtime-kit uses Cortlet to handle persistent WebSocket connections while the application backend remains serverless.

Infrastructure

Realtime transport

WebSocket infrastructure provided through Cortlet.

Powered by Cortlet

Compatibility

This project is designed to integrate with Cortlet and can be used alongside other supported serverless tools.

Works with Cortlet
Good placement

Project header

Useful when Cortlet is part of the project's implementation.

Good placement

Technology section

Useful when explaining infrastructure or runtime dependencies.

Good placement

Compatibility section

Useful when documenting supported integrations.

01

Keep context

Place the badge where readers can understand what relationship it represents.

02

Keep it secondary

The repository or project name should remain more prominent than the Cortlet badge.

03

Link appropriately

When clickable, point the badge to an official Cortlet page relevant to the integration.

Example 03 // Integrations

Integration pages

Show compatibility without implying endorsement.

Cortlet can appear in integration directories and technology lists when the relationship is accurate and clearly described.

Use Works with Cortlet for compatibility and integration listings.

Keep Cortlet visually consistent with other supported technologies.

Do not make Cortlet look like a sponsor, owner, or exclusive technology partner unless that relationship actually exists.

acme.example/integrations
ACMEIntegrations

Supported technologies

Connect the tools you already use.

ACME works with several infrastructure and developer platforms. Each integration remains independently operated by its respective provider.

Cortlet

Realtime WebSocket infrastructure.

Works with Cortlet

Neon

Postgres database connectivity.

NEON

Vercel

Serverless application deployment.

VERCEL

Resend

Transactional email delivery.

RESEND

Choose by relationship

Works with
Appropriate when true

Works with

Best for compatibility, integrations, connectors, and supported technology lists.

Built with
Appropriate when true

Built with

Best when Cortlet is one of the technologies used to build the product.

Powered by
Appropriate when true

Powered by

Best when Cortlet provides meaningful underlying functionality or infrastructure.

01

Equal treatment

Do not artificially make Cortlet much larger than other technologies in the same integration list.

02

Accurate relationship

The badge wording should match what Cortlet actually does for the product.

03

No endorsement

Compatibility alone does not mean Cortlet sponsors, certifies, or endorses the product.

Example 04 // Footer attribution

Footer attribution

Keep attribution visible, but secondary.

Cortlet badges can be used in website footers, product footers, and attribution areas when the badge accurately describes the relationship.

Keep the badge smaller and less prominent than the product's own identity.

Give the badge enough clear space from navigation, copyright text, and other logos.

Use the badge wording that truthfully reflects the relationship with Cortlet.

acme.example
ACME

Fictional developer platform

Infrastructure that stays out of your way.

ACME is a fictional example showing where Cortlet attribution can appear without overpowering the site's own identity.

ACME

© 2026 ACME // FICTIONAL EXAMPLE

Infrastructure attributionPowered by Cortlet
Built with Cortlet
Good use

Built with Cortlet

Good for product footers when Cortlet is part of how the product was built.

Powered by Cortlet
Good use

Powered by Cortlet

Good for infrastructure attribution when Cortlet provides underlying functionality.

Works with Cortlet
Good use

Works with Cortlet

Good for integration or compatibility footers where Cortlet is one supported technology.

01

Secondary placement

The site or product identity should remain visually dominant.

02

Clear spacing

Keep enough space around the badge so it does not feel attached to unrelated footer elements.

03

Use the correct claim

Choose Built with, Powered by, or Works with based on the actual technical relationship.

Quick reference

Accurate first.
Attractive second.

Use the badge whose wording accurately describes the relationship with Cortlet.

Keep your own product or organization visually primary.

Do not stretch, recolor, rebuild, or materially modify official Cortlet badge artwork.

Keep enough clear space around badges so surrounding content does not make them feel crowded.

Badge usage does not imply Cortlet partnership, certification, sponsorship, or endorsement.

More brand guidance

Keep the
relationship clear.

CORTLET // BRAND // BADGES