Social posts and carousels, made by RUPA
RUPA makes the images for organic social: carousel frames, posts sized for Instagram, LinkedIn, X, Facebook and Pinterest, and video thumbnails. Each preset fixes the size and the number of plates, and the workspace's brand guidelines go with every render.
The presets RUPA works from
Carousel frames
Four frames from one brief, with consistent ground and light across every frame.
1024 by 1536, tall, four plates, 6% safe margin
Instagram square post
One clear subject, bold enough to stop a scroll, with space for a short line of copy.
1024 by 1024, square, four plates, 6% safe margin
LinkedIn post
A calm, professional visual for a feed post: one idea, one subject, room for a title.
1536 by 1024, wide, three plates, 5% safe margin
X post
High contrast and legible small, with the subject centred so a feed crop keeps it.
1536 by 1024, wide, three plates, 6% safe margin
Facebook post
Warm and people first, the subject large, a short headline if the brief has one.
1024 by 1024, square, four plates, 6% safe margin
Pinterest pin
A tall, aspirational image with a title band near the top.
1024 by 1536, tall, three plates, 6% safe margin
Video thumbnail
One face or one object, readable at 168 px wide.
1536 by 1024, wide, four plates, 4% safe margin
How RUPA runs it
- 01
Brief
A person writes the brief in her studio and picks the feed preset. From the Content room, an @RUPA message gets one brand-locked plate at a size and a quality; presets, references and attachments are in her studio only.
- 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.
- 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.
- 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.
- 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 personWaits for a person to approve the plan card, where the workspace has not let RUPA render on her own.
- 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.
- 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.
- 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 RUPA needs from you
Brand book
The brand guidelines Brand Lock sends with every render, and the banned words and manual rules the Brand check reads.
Logo
The workspace's own mark, sent as an image when Brand Lock and the mark are both on.
References
Nagent's shared reference set or the workspace's own uploads, for a look to borrow.
Attachments
Images from the Knowledge Hub or the Asset Library that must appear in the render.
What is governed
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.
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.
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.
An audit row per render
Every render that reaches the image model is written to the audit log with how it was authorised.
Questions about RUPA
Does RUPA make carousels?
Yes. Carousel frames renders four frames from one brief, tall at 1024 by 1536, with consistent ground and light across every frame. They are four plates from one request, not frames planned one by one.
Which social formats can RUPA make?
Instagram square post and Facebook post render four square plates at 1024 by 1024. LinkedIn post and X post render three wide plates at 1536 by 1024. Pinterest pin renders three tall plates at 1024 by 1536, and Video thumbnail four wide plates.
Does RUPA publish the posts?
No. RUPA makes the images and files them in the Asset Library, which is also the Assets tab of the Knowledge Hub. MOXA, coming soon, will ask her for a post's image.
Will every post look like our brand?
Brand Lock is on by default, so the brand book's guidelines go with every render and the bench shows the exact text sent. An image model knows nothing about a brand unless it is told, every time.
Can I ask RUPA from a team room?
Yes. In the Content room, type @ and pick RUPA, and she renders one brand-locked image from the message: square, wide or tall, standard or HD. Presets such as Carousel frames are in her studio only.
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.