Press kit

Writing about REAP

Boilerplate you can paste, facts you can check, the words we use, logos you can use, and a person who answers. For interviews, briefings and background, use the press door on the contact page.

Press and analyst inquiries

Boilerplate

Two lengths

Short (42 words)

REAP is the agentic AI platform for network operations: the reasoning and assurance layer above the tools enterprises already run. It explains incidents with evidence, checks changes before and after they land, and tests whether redundancy will hold before it is needed.

Long (119 words)

REAP is the agentic AI platform for network operations. Built by the engineers behind Andiamo (opens in a new tab), Insieme (opens in a new tab), Pensando (opens in a new tab) and WiteSand (opens in a new tab), REAP observes an enterprise’s network and IT systems, reasons over live evidence the way a senior engineer does, and acts only under the customer’s governance: read-only by default, approval-gated when it acts, with every conclusion traceable to the evidence. REAP is built to explain incidents in minutes rather than war rooms, to check changes made anywhere before and after they land, and to prove that failover will work before it has to. It is in proof-of-value pilots with design partners. REAP runs as SaaS today, with deployment in the customer’s cloud or on-premises by arrangement. Headquartered in San Jose, California.

Facts

Checkable

Company: Reapitnow.ai, Inc., doing business as REAP
Founded by: Raja Rao Tadimeti, Natarajan “Nata” Manthiramoorthy, Madhava Cheethirala
Headquarters: 2150 North First Street, Suite 513, San Jose, CA 95131
Category: Agentic AI for network operations (agentic NetOps software)
Headline: From signals to answers.
Tagline: Agentic Network Assurance. Grounded in Evidence.
Method: Observe · Reason · Act · Prove
Statements: Restored ≠ Fixed · Completed ≠ Verified · Configured ≠ Compliant (the written forms)
Backing: Venture-backed by two venture firms and angels
Team: Founding team with 32 granted US patents (list); careers at Cisco (opens in a new tab), Juniper (opens in a new tab), Aruba (opens in a new tab), VMware (opens in a new tab), Innovium (opens in a new tab) and F5 (opens in a new tab)
Deployment: SaaS (REAP Cloud) today; Customer Cloud (AWS (opens in a new tab), Azure (opens in a new tab), GCP (opens in a new tab)) and Customer On-Prem by arrangement
Events: ONUG Fall 2026 (opens in a new tab), New York, October 28–29: sponsor and speaker, Booth 33; Raja Tadimeti presents “The Change Succeeded. Did the Network? Building Confidence in Change Outcomes” on October 29 at 3:15 pm ET. AutoCon 6, Tucson, November 16–20: supporting sponsor
Website: reapnet.ai

The words

Four lines, each with one written form

What REAP says about itself, as it is written on the website, in documents, on slides and on the banner. Copy them as they are.

Headline

From signals to answers.

Sentence case, with the period. The message line: it leads the home page, the explainer and the event banner. In display text “answers.” takes Meridian Blue.

Tagline

Agentic Network Assurance. Grounded in Evidence.

Written as shown: two short sentences in title form, each ending with a period; no trademark symbol. Never reworded, abbreviated or translated. It signs the page: beside the logo, under the method line, next to the address.

Method line

Observe · Reason · Act · Prove

The four steps in this order, separated by middle dots. Prove is the fourth step, and takes Meridian Blue in display text: REAP keeps the evidence for every conclusion.

The three statements

Incident Reasoning

Restored is not Fixed

Restored is not the same as fixed.

Accelerate root-cause analysis.

Change Assurance

Completed is not Verified

Completed is not the same as verified.

Validate change outcomes.

Resilience Assurance · posture & compliance

Configured is not Compliant

Configured is not the same as compliant.

Uncover operational risks.

Three sentences, always together and in this order: each names a gap that a green dashboard hides. The ≠ form is for display (banners, slides, titles) and the sentence for running text; the line under each is what REAP does about it. Write the closing word in Meridian Blue where the text is display size.

House style: sentence case for headings and statements; no capitals for emphasis; the company is REAP (Reapitnow.ai, Inc.) and the address is written reapnet.ai, lowercase; no performance figures beside the tagline; no third-party names in the same line as any of the four.

Leadership

Available for interviews

Raja Rao Tadimeti

Co-founder & CEO

Co-founder of WiteSand (opens in a new tab) (acquired by Juniper Networks (opens in a new tab)); founding engineer at Pensando (opens in a new tab) and Insieme (opens in a new tab); decades shipping networking products at Cisco (opens in a new tab) and Juniper (opens in a new tab). Speaks on evidence-backed operations and the economics of network incidents.

Natarajan “Nata” Manthiramoorthy

Co-founder · Customer Success & Solutions Engineering

Early engineer at WiteSand (opens in a new tab), Pensando (opens in a new tab), Innovium (opens in a new tab), Insieme (opens in a new tab), Aruba (opens in a new tab), and Andiamo (opens in a new tab). Runs deployments, security and onboarding. Speaks on deploying AI in regulated networks.

Madhava Cheethirala

Co-founder · VP of Engineering

Co-founder of WiteSand (opens in a new tab); built networking products at Cisco (opens in a new tab) (Insieme (opens in a new tab), Andiamo (opens in a new tab)), VMware (opens in a new tab) and Juniper (opens in a new tab). Owns the reasoning engine, agents and platform. Speaks on how agents reason over networks and how they are governed.

Rishit Lakhani

Head of Solutions Engineering

Works with network operations teams evaluating agentic AI. At ONUG Fall 2026 (opens in a new tab) with the team at Booth 33: the demos and the twenty-minute meetings.

Todd Yancey

Strategic Advisor

Twenty-five years building enterprise B2B software revenue. Speaks on how buyers should evaluate agentic AI and on proof-of-value design.

Logos

The REAP logo and the R

The logo, the backgrounds it goes on, the space it needs and what never to do with it.

Download the REAP logo pack (every official colorway, SVG, PDF and PNG) ZIP · the logo and the R mark, one folder per colorway named for where it goes; app icons; a README with the rules

REAP Brand Guidelines (PDF) logo, color, type, words and files, in one document

Which logo on which background

On white · preferredNavy with the Light Blue foot: the most common useSVG · PNG

On white · alternateAll navy, on white or a very light backgroundSVG · PNG

On Meridian · preferredWhite with the Light Blue foot: a fuller brand presenceSVG · PNG

On Meridian · alternateAll white, on a flat Meridian fieldSVG · PNG

On a dark fieldWhite with the Light Blue foot: product UI, small-size collateralSVG · PNG

On the Meridian gradientWhite with the Light Blue foot: contemporary contexts such as AISVG · PNG

Grayscale and the R

Grayscale · preferredGray-900 with a Gray-500 footSVG · PNG

Grayscale · alternateAll Gray-900, on white or a very light backgroundSVG · PNG

BlackA safe, neutral option where color is not availableSVG · PNG

White on blackFor a dark one-color contextSVG · PNG

The R aloneWhere the full logo does not fit, and for the favicon. It needs no background.SVG · PNG · white SVG

Clear space and size. Keep a space the size of the R (x, as wide as it is tall) between the logo and the next element, on every side. Do not use the logo below 16 px high. Where the full logo does not fit, use the R.

Don’ts

Always keep the core visual qualities of the REAP mark: use the files as supplied.

Don’t change the colors

Don’t distort it

Don’t tilt it

Don’t change the letters or their spacing

Lockups: the logo with a line beneath it

Download the lockups (SVG and PNG, both colorways) with the REAP QR code ZIP · eight lockups, the QR code, and a README with the rules

Wordmark + the tagline · for light backgroundsPNG · SVG

Wordmark + the headline · for light backgroundsPNG · SVG

Wordmark + the method line · for light backgroundsPNG · SVG

Wordmark + the descriptor · for light backgroundsPNG · SVG

Wordmark + the tagline · for Meridian and dark backgroundsPNG · PNG on Meridian-950 · SVG

Wordmark + the headline · for Meridian and dark backgroundsPNG · PNG on Meridian-950 · SVG

Wordmark + the method line · for Meridian and dark backgroundsPNG · PNG on Meridian-950 · SVG

Wordmark + the descriptor · for Meridian and dark backgroundsPNG · PNG on Meridian-950 · SVG

A lockup is the logo with one line beneath it, left-aligned and sized to the logo’s width: the light files carry the navy logo with the Light Blue foot, the dark files the white logo with the Light Blue foot. Keep the clear space of the R around the whole lockup. Use a lockup where the logo stands alone with a caption: a slide or document cover, an event listing, a sponsor page, a social header, an email signature. Use the plain wordmark where the words already appear nearby. Do not set your own caption under the wordmark; use these files.

Color

Meridian, REAP Gray and the status colors

REAP has one brand hue, Meridian (HSL 198, 55, x), and a neutral that carries the same hue, REAP Gray (HSL 198, 10, x). Each runs from 10 (lightest) to 1000 (darkest); the number after L is the lightness. Click a value to copy it.

Meridian · the brand

Meridian-10L 96
Meridian-50L 94pale panels
Meridian-100L 90
Meridian-200L 86
Meridian-300L 84
Meridian-400L 70Light Blue · the foot
Meridian-500L 60
Meridian-600L 50Meridian Blue · accents
Meridian-700L 40
Meridian-800L 30links on white
Meridian-900L 20
Meridian-950L 14navy · the logo on white, the dark field
Meridian-1000L 4

REAP Gray · text and surfaces

Gray-10L 96subtle surfaces
Gray-50L 94
Gray-100L 90
Gray-200L 86borders
Gray-300L 84
Gray-400L 70
Gray-500L 60the grayscale foot
Gray-600L 50
Gray-700L 40secondary text
Gray-800L 30
Gray-900L 20text
Gray-950L 14
Gray-1000L 4

Status colors · for status only

Viridian · healthyhsl(161 68% 44%) · subtle #E5FAF4

Crimson · alerthsl(339 100% 42%) · subtle #FFE5EE

Solar · warninghsl(31 100% 55%) · subtle #FFEEDB

The triad is shifted on purpose from the usual red, yellow and green, and it marks status only: never decoration. On white, set status words in a darker shade of the same hue (or in Gray-900 beside a colored dot) so they stay readable.

Color files: CSS variables · JSON · Adobe swatches (ASE)

Typography

DM Sans for text, DM Mono for technical data

DM Sans · all text

From signals to answers.

Agentic Network Assurance. Grounded in Evidence.

Observe · Reason · Act · Prove

REAP reasons across every information island to surface root cause in minutes, not hours.

Weights 400, 500, 600 and 800: Regular for reading, Medium for labels and buttons, SemiBold for headings, ExtraBold for display lines and big numbers.

DM Mono · numerical and technical data

plant-a-core-2# show ip ospf neighbor
Neighbor ID   Pri  State     Dead Time  Interface
10.20.5.1       1  FULL/DR   00:00:34   Vlan350
10.20.50.1      1  FULL/BDR  00:00:31   Po1

02:07:40  CHG-2041  TCP 443  10.20.50.0/24

IP addresses and subnets, ports, commands and CLI output, log timestamps, and the identifiers of devices, interfaces, changes, incidents and runbooks. Metrics and KPI numbers stay in DM Sans.

The REAP type scale
Style	Size	Weight	Use
Display	48 px	ExtraBold 800, tracking −0.02 em	Website hero lines
Heading 1	24 px	SemiBold 600	Page titles
Heading 2 · 3	20 · 16 px	SemiBold 600	Section headers, card titles
Body	14–16 px	Regular 400	Running text
Label	13 px	Medium 500	Buttons, badges, navigation
Overline	11 px, capitals	SemiBold 600, tracking 0.08 em	Section labels such as STATUS
Metric	32 · 24 px	ExtraBold 800 · SemiBold 600	KPI numbers
Code	13 px	DM Mono 400	IPs, commands, configuration values, CLI output

Both typefaces are free under the SIL Open Font License: DM Sans (opens in a new tab) and DM Mono (opens in a new tab) on Google Fonts. In print and in documents, the same rule applies: REAP’s Word files carry both fonts; for slides and spreadsheets, install them from the logo pack’s README links.

Interaction

How the website answers the pointer and the keyboard

Two treatments every page shares, as the brand guidelines describe them.

Interactive surfaces

Rest the pointer on this card. Every card, tile, row and panel on the site answers the same way: the border turns Meridian Blue, the surface rises 2 px with a soft shadow, and the change takes 220 ms. Keyboard focus inside a surface lights it the same way, so a keyboard user sees what a mouse user sees. Dark surfaces brighten one step instead of rising; forms and diagrams highlight without moving. Where the visitor asks for reduced motion, the highlight stays and the movement goes; print drops both.

One block of the stylesheet carries the rules; a new component that uses the card classes gets the treatment without new CSS.

Accessibility statement

Glossary links

The first mention of a glossary term on a page is a quiet link with the definition as its tooltip, like these: the OSPF neighbor never changed state, so the runbook waited for the change window and the postmortem recorded why.

Headings, buttons, navigation, code, forms and the glossary itself are never linked, and a page carries at most 24 links. The build applies the links from the glossary data (244 terms in 10 groups); the WordPress plugin applies the same rules to blog excerpts, search results and posts written in the editor. A search for a term or one of its other spellings shows the definition above the results.

The glossary

QR code

One code that opens reapnet.ai

The REAP QR code

Opens reapnet.ai. Use it on anything printed or projected that points to REAP: an event listing, a sponsor page, a slide, a sign.

PNG · SVG

Print it at 0.8 inch (20 mm) or larger, in Meridian-950 or black on white, with the white margin the file includes (four modules) left clear. The R mark at the center is part of the code: do not replace it, recolor it or move it, and do not add a frame or a caption inside the margin. It is a standard QR code and reads on any phone camera.

Using the brand

For partners, press and events

Use the files from the logo pack as supplied; never redraw or retype the logo.
On white, use the navy logo with the Light Blue foot; on Meridian or a dark field, the white logo with the Light Blue foot.
Keep the clear space of the R on every side, and 16 px as the smallest height.
Write REAP in capitals; the company is Reapitnow.ai, Inc.; the address is reapnet.ai.
Use the words as written on this page.
Questions, or a use not covered here: press and analyst inquiries.

Images

The banner, the film, the people

The event banner

The retractable banner that stands with the team at events (33 × 79 in): one navy field, one typeface, everything on one axis. Reading down: the wordmark; the headline; the three statements, each with its line; the method line with the tagline beneath it; the address and the QR code.

From signals to answers.
Restored ≠ Fixed · Accelerate root-cause analysis.
Completed ≠ Verified · Validate change outcomes.
Configured ≠ Compliant · Uncover operational risks.
Observe · Reason · Act · Prove
Agentic Network Assurance. Grounded in Evidence.
reapnet.ai

Download the banner as an image (PNG, 150 dpi, 1 MB)

The banner’s own QR code opens reapnet.ai too; for anything you print, use the REAP QR code above rather than a photograph of the banner.

The film

REAP in 90 seconds, the explainer that opens the home page: what a green dashboard hides, and what evidence-backed assurance looks like. No sound; captions in the picture.

Download the film (MP4, 720p, 1.4 MB) · Poster frame (JPG)

Headshots and product images

Headshots of the founders and product images are available on request through the press door on the contact page. Screenshots on this site show illustrative data and are labeled as such.

Recent

News and appearances

Event · Oct 28–29, 2026

REAP at ONUG Fall 2026, New York

Sponsor and speaker. Raja Tadimeti presents “The Change Succeeded. Did the Network? Building Confidence in Change Outcomes” in the Tools, Technologies & Techniques theater on October 29 at 3:15 pm ET.

Event details

White paper

Why REAP: evidence-backed network assurance for the agentic era

Fourteen pages, including ten autonomous-agent scenarios for network teams.

Read the summary

Blog

Field notes from the team

Practitioner writing on incident, problem, and change management, build versus buy, and change verification.

All posts

Need a quote or a briefing?

We reply to press and analyst inquiries within one business day.

Press and analyst inquiries