Skip to content
NagentNagent
Log inSign upHire your AI team
NagentNagent
Teams
The Growth Org
Create, Content, led by CREACREARUPAFOLIOAlpha (Beta)Kinetiq
Serve, Customer experienceConvexa
Platform
Customers
Log inSign up
Artefacts
Nagent ThesisState of Agent GovernanceMultiplayer AIThe Agentic Marketing ThesisThe Answer LayerThe Outbound ThesisAll artefacts
Learn
Nagent Resources HubNagent BlogsComparisons
Dev & Technology
Developer DocsAI ModelsTools & IntegrationsSecurity & Compliance
Enterprise and White Glove
Nagent AI LabsNagent Enterprise
Company
PricingAboutFAQContact us
Made by RUPA

Logo marks and profile pictures, made by RUPA

RUPA makes a simple logo mark on a transparent ground, and profile pictures built for a circle crop. Each preset renders four square plates.

Hire RUPATalk to us
Presets

The presets RUPA works from

01

Logo mark

A simple mark on a transparent ground, readable at 32 px, no small text.

1024 by 1024, square, four plates, 12% safe margin, transparent background

02

Profile picture

One face or one mark, centred inside the circle crop, nothing important in the corners.

1024 by 1024, square, four plates, 15% safe margin

How it runs

How RUPA runs it

  1. 01

    Brief

    A person writes the brief in her studio and picks Logo mark or Profile picture. Both fix a square size and four plates.

  2. 02

    Brand Lock

    Brand Lock is on by default, so the workspace's brand guidelines go with the render and the bench shows the exact text sent. With the mark switched on, the workspace's own logo travels as an image to be placed, never redrawn; without it, the image model is told to draw no logo at all.

  3. 03

    Reference

    A reference image is optional. It comes from Nagent's shared set or the workspace's own uploads, with one of five intents: match the style, reproduce the layout, change the headline, localise it or remix it. Each intent says what it keeps and what it drops.

  4. 04

    Attachments

    Images that must appear, such as a product shot, are attached from the Knowledge Hub or the Asset Library. A render takes at most ten input images, the logo and the reference included.

  5. 05

    Plan card

    RUPA renders on her own where the workspace allows it. Otherwise she writes a plan card with the estimated spend, and nothing renders until a person approves it.

    Waits for a person

    Waits for a person to approve the plan card, where the workspace has not let RUPA render on her own.

  6. 06

    Render

    Before anything is sent, her budget and a per-action cap for the batch are checked against the estimate. Over either, she refuses and names the limit. Then she renders the plates.

  7. 07

    Brand check

    A Brand check card follows the sheet. It reads the brief against the brand book's banned words and marks the rules a text check cannot confirm as "Needs your eye". It judges what RUPA was told, not what she made.

  8. 08

    On the record

    Every render that reaches the image model writes an audit row saying how it was authorised, and the plates are filed in the Asset Library, which is also the Assets tab of the Knowledge Hub.

What you supply

What RUPA needs from you

01

Brand book

The brand guidelines Brand Lock sends with every render, and the banned words and manual rules the Brand check reads.

02

Logo

The workspace's own mark, sent as an image when Brand Lock and the mark are both on.

03

References

Nagent's shared reference set or the workspace's own uploads, for a look to borrow.

04

Attachments

Images from the Knowledge Hub or the Asset Library that must appear in the render.

Governance

What is governed

01

Brand Lock by default

The workspace's brand guidance goes with a render unless a person turns it off, and the bench shows the exact text sent.

02

A Brand check that reads the brief

It reads the brief for banned words and marks what text cannot show as "Needs your eye". It does not look at the plates, so a person does.

03

Budget before every render

Her budget and a per-action cap for one batch are checked before anything is sent, and a render over either is refused with the limit named.

04

An audit row per render

Every render that reaches the image model is written to the audit log with how it was authorised.

Questions

Questions about RUPA

01

Does the logo mark come back on a transparent background?

Yes. A mark is placed on other people's grounds, so the Logo mark preset asks for a transparent background. It renders four square plates at 1024 by 1024, readable at 32 px with no small text.

02

Will a profile picture survive a circle crop?

The Profile picture preset centres one face or one mark inside the circle crop and keeps anything important out of the corners, with a 15% safe margin on four square plates.

03

Can RUPA cut a subject out of a plate?

Yes. Cut out takes a plate she has rendered and saved, isolates the subject on a clean transparent background and drops the shadow, one image per run.

04

Who decides when RUPA spends money?

The workspace. Where RUPA may not render on her own, a plan card shows the estimated spend and nothing renders until a person approves it. Either way, her budget and a per-action cap are checked before anything is sent.

05

How much does RUPA cost?

RUPA works on the Content team. Nagent plans are Solo at $29.99 a month ($19.99 billed annually), Team at $299 a month ($199 billed annually) and Business at $1,499 a month ($999 billed annually). Enterprise is by quote. The pricing page shows which teams each plan includes.

Pricing

RUPA works on the Content team. Nagent plans are Solo at $29.99 a month ($19.99 billed annually), Team at $299 a month ($199 billed annually) and Business at $1,499 a month ($999 billed annually). Enterprise is by quote. The pricing page shows which teams each plan includes.

See all plans
Hire RUPA