BRAND / OPSKNIGHT

One identity.
A clear signal.

Incident operations you control. The identity pairs operational surfaces with a deliberate red signal and enough restraint for the product to remain the focus.

Download SVG logo Download PNG

THE MARK

Keep the knight recognizable.

Use the supplied mark, preserve its proportions and leave clear space around it.

Use the original vector wherever possible. The PNG is provided for environments that cannot use SVG.

SVG asset PNG asset Web mark

Clear space

Give the knight mark breathing room. Do not crowd it with text, borders or partner marks.

Keep proportions

Scale the supplied asset as one unit. Do not stretch, squash, rotate or redraw the mark.

Use contrast

Use the red mark where it remains legible. Prefer the supplied assets over recoloring the logo.

Name it OpsKnight

Write the product name as “OpsKnight”. Avoid alternate spacing, abbreviations or invented product names.

COLOR

Operational, not decorative.

OpsKnight Red#D21A1B

Command Black#0B0F18

Ops Slate#0F172A

Elevated Slate#1E293B

Canvas#F8FAFC

Ink#111827

Operational Green#059669

Warning#D97706

USE IT CORRECTLY

Practical rules for product references.

Keep the name, mark and product claims recognizable and accurate wherever OpsKnight appears in documentation, integrations or partner material.

Preserve the supplied identity.

Use “OpsKnight” with the exact capitalization.
Use supplied logo assets with clear space and sufficient contrast.
Describe the product using capabilities that are current for the referenced release.
Link to the project or documentation when attribution helps readers verify a claim.

DON’T

Invent variants or implied endorsements.

Do not stretch, rotate, recolor, or redraw the knight mark.
Do not call a third-party product or service an official OpsKnight offering without permission.
Do not combine the OpsKnight name with another brand in a way that implies ownership or endorsement.
Do not reuse old release claims as if they describe the current product.

README & DOCS

Present OpsKnight consistently.

Use the canonical mark, product name and current-release wording when OpsKnight appears in a README, integration guide or partner document.

README LOCKUP

Keep the product name and destination obvious.

![OpsKnight](https://opsknight.com/logo.svg)

**OpsKnight** — self-hosted incident management and on-call.

[Install](https://opsknight.com/deploy/) · [Docs](https://opsknight.com/docs/) · [GitHub](https://github.com/opsknight-labs/OpsKnight)

INTEGRATION ATTRIBUTION

Describe interoperability without implying endorsement.

Works with OpsKnight v2.0.0 through the documented webhook/API contract.

OpsKnight is an independent open-source project. Product names and trademarks belong to their respective owners.

THE INCIDENT SIGNAL

Red carries meaning.

A point, a path, an active incident. Use red to explain routing, paging, attention and action—not as decoration on every surface.

TYPOGRAPHY

Type with clarity.

Manrope leads narrative copy. JetBrains Mono labels versions, commands, states and operational details. Large headings should create hierarchy, not crowd smaller laptop viewports.

TRADEMARK & ATTRIBUTION

Identify the project without implying affiliation.

The OpsKnight name and logo identify this project and product. When referencing OpsKnight from another product, company or service, keep the attribution clear and do not imply endorsement, certification or an official partnership that has not been established.

WRITING

Specific beats dramatic.

Describe what the product actually does, its operational boundaries and where to verify the behavior. Avoid unsupported superlatives or claims that a deployment has not proven.

One identity.A clear signal.