Brand Guidelines
BOILERPLATE
Yellowbrick is a modern SQL data platform for enterprise data warehousing, ad-hoc and streaming analytics, AI and BI workloads. Yellowbrick offers unparalleled speed and scalability with minimal infrastructure, deployable across public and private clouds, data centers, laptops and the edge; providing a private data cloud experience that ensures data stays under your control to meet residency and sovereignty needs. Yellowbrick Data was founded in 2014 and is headquartered in Mountain View, CA. Learn more at yellowbrick.com and visit us on LinkedIn and Twitter.
main colors
HEX #FFDB2C
PMS Yellow C
CMYK 0•10•100•0
RGB 255•219•44
HEX #86BC4D
PMS 367 C
CMYK 53•5•93•0
RGB 134•188•77
HEX #55ACBA
PMS 2233 C
CMYK 65•15•25•0
RGB 85•172•186
HEX #F29C11
PMS 1375 C
CMYK 3•44•100•0
RGB 242•156•17
HEX #FFFFFF
PMS 11-0601 TCX
CMYK 0•0•0•0
RGB 255•255•255
HEX #000000
PMS Black 6 C
CMYK 100•100•100•100
RGB 0•0•0
logo
Our logo is the entryway to our brand. The Yellowbrick logo is the visual representation of the benefit to our customers and prospects. A secure, efficient, and flexible data platform that can be deployed wherever your data is and ensures data always stays under your control.
Typeface
Manrope
ABCDEFGHIJKLMNOPQRSTUVWXYZ
ABCDEFGHIJKLMNOPQRSTUVWXYZ
Typography plays a significant role in projecting the Yellowbrick image and visual style. Whenever possible, Manrope is the primary typeface across our communications design system.
Note: If you are unable to use the Manrope font in Microsoft Office documents, then Aptos is an acceptable alternative.
Trademarks
Yellowbrick's patented Direct Data Accelerator® is a registered trademark and represents intellectual property rights owned by Yellowbrick.
Usage Guidelines:
- In letters, memos, press releases, white papers, advertising, slides, video, and other multimedia presentations, ensure that you properly identify (with ®) each Yellowbrick Trademark at the most prominent use (often in the headline) and again in the first occurrence. For presentation graphics, each Yellowbrick Trademark should be designated with the proper trademark symbol on each page and slide;
- In newsletters, magazines, and publications containing multiple articles, properly identify each Yellowbrick Trademark in the first occurrence in the Table of Contents, in headlines and in the first occurrence in every article in which it is used;
- In brochures, books, white papers, data sheets, technical documentation, and other bound documents, properly identify each Yellowbrick Trademark in the first occurrence in the Table of Contents, in headlines, and in the first occurrence in text;
- In all charts and graphs, properly identify each Yellowbrick Trademark, as such charts and graphs could become separated, copied and used independently
hierarchy
H1
font-size: 64px
The private data cloud
H2
font-size:40px
DEVELOPERS
H3
font-size:24px
Data Control
H4
font-size:16px
Yellowbrick for
H5
font-size:20px
Simplify your enterprise’s data management and lower costs for cloud and on-premises platforms with Yellowbrick.
P
font-size:16px
Deploy in your Azure, AWS, GCP, data center, or edge environments while staying compliant with policies and data residency requirements.
email signature
EDIT NAME
Edit position
Phone 916.316.9867 | 660 W Dana St, Mountain View, California, 94041 | Website yellowbrick.com
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
EDIT NAME
Edit position
Phone +16506870896 | 60 Trafalgar Square London, WC2N 5DS UK | Website yellowbrick.com
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.