A content operations platform. One strategy drives everything — SEO articles, social posts, finished video — generated, reviewed, published and tracked in one place, where every move the machine wants to make is a proposal you approve.
Strategy, studio, publishing, analytics. The platform works the content. You approve, reject, or edit — nothing ships without you.
A narrated walk through one quarter of Fjord & Pine, the demo brand this whole page runs on — the strategy drafted, a brief fanned out, cuts rendered, the SEO matrix expanded, the queue decided, and what came back. Every frame is the product's own chrome: the same screens, the same data and the same palette as the live scenes below.
Rendered with narration and score, like the Stratus films — same Atlas palette, different product. The figures it shows are the same figures on the strategy and performance boards below.
A keyword tool, a writing tool, a scheduler, a video editor, an analytics tab per platform — and the strategy in a slide deck nobody opens. Nimbus holds all of it as one model: every piece of content knows which strategy slot it serves, where it will publish, and what came back.
Which of our nine tools owns this post?
Who is writing this week’s content?
What is this piece for, and what may happen to it next?
Both halves of that answer live in the platform. A piece is an object with a purpose and a lifecycle — and the lifecycle is made of actions you approve.
Give it the brand brief, the channels and last quarter's numbers, and the strategist drafts a 90-day plan — pillars, keyword clusters, a channel calendar. You approve the week in one pass or reject a slot with a reason. It never silently rewrites the plan; revisions arrive as diffs.
strategy.proposeslot.approveslot.rejectstrategy.revisepillars → clusters → calendar, drafted from the brand brief and last quarter’s numbers
approve the week in one pass, or reject a slot with a reason the strategist learns from
when a cluster stalls or a post outperforms, the revision arrives as a diff — never a silent rewrite
A brief is one strategy slot made concrete. The studio takes it and drafts the whole set: the SEO article with its outline, meta and internal links; per-channel posts written for each channel, not pasted across them; and a video storyboard that renders to finished cuts.
The video column is not a mock. Approve the storyboard and the pipeline scripts, lays out and renders the cut in 16:9, 9:16 and 1:1, brand kit applied — the film above walks that exact flow.
One brief can also become a corpus. The planner turns an idea into axes and a section blueprint, expands the matrix, and generates every page against the brand's fact book. A quality gate bounces prose that is too long, off-doctrine or too similar to its siblings — with directive feedback, not 'try again'. A fact-checker then verifies grounding: every concrete claim must match a recorded fact, or the page flags and waits. This engine is not a roadmap item — it already runs a production site; Nimbus inherits it whole.
A guide for every wood × finish combination we sell — what to oil, what to avoid, how often. Link each guide to its collection.
word windowevery section inside its band — and the retry prompt is directive: “210 words, the target is 60–160”, never “try again”banned phrasesthe doctrine list — the words your brand never says, enforced at generation timesimilarity ≤ 0.555-gram overlap checked against sibling pages in the same language — 36 guides, no two allowed to blur togetherRegeneration is deterministic: voice, angle and layout derive from a hash of the page key, so a re-run reproduces identical pages and a resumed campaign skips everything whose inputs did not change. Renamed URLs write 301s with chain collapse; canonicals, hreflang alternates and the sitemap all come from the same pages table.
Everything that would leave the platform — a post, an article, a video upload, a comment reply — goes through the same pipeline, whoever drafted it. Agents run in propose mode: their work stops at review and waits for you.
The approvals queue doubles as the audit trail: what was proposed, what you changed, what shipped, and what it earned — one record per piece, never pruned.
Edit-and-approve opens the draft in the real editor — the post, the article, the storyboard — and one click ships your amended version as your own action, rejecting the original with a reason the drafting agent learns from.
article.publishpendingWordPress draft ready · meta + schema set · 4 internal links
Every card carries the draft, the evidence behind it, and exactly what will happen where. Edit-and-approve files your version as your own action.
Auto, propose, or manual — per channel and per verb. Let the newsletter schedule itself, keep TikTok replies on propose, keep anything touching the blog behind your approval. The default everywhere is propose.
Reject three drafts for the same reason and the pattern is written down as a voice rule you confirm once. Every confirmed rule calibrates every draft after it — tone, claims, hooks, length.
Connect a channel once with OAuth and it becomes two pipes: proposals flow out through the channel's own publishing API, and its numbers and comments flow back to the pieces that earned them.
A channel never sees an unapproved draft. Tokens live in an encrypted vault; revoke a channel and its queue freezes — it never leaks.
The mailer we run in production at nuage.ee — identities, contacts, groups, templates, campaigns, follow-up sequences with response detection — rebuilt inside Nimbus with the AI layer on top. Campaigns are drafted from the strategy, sequences stop themselves the moment someone replies, and every send sits in the same approval queue as everything else.
The Friday newsletter slot is a campaign. The issue is drafted from what shipped that week — in the brand voice, against the fact book — and waits in the queue like everything else.
Contacts imported and deduplicated, groups kept clean, and behaviour-based segments — clicked twice, went quiet, bought once — proposed by the platform, never applied silently.
Sequences send until someone responds — response detection cancels the rest of the thread the moment a reply lands. The reply itself joins the same triage queue, with an answer drafted.
Sending identities and SMTP tested before a single send, failures retried with backoff, and per-recipient opens, clicks and bounces joined back to the campaign — and to the strategy behind it.
The sending engine is proven on our own outreach: contact import with dedupe, per-recipient delivery stats, failed-send retry, scheduled follow-ups cancelled on reply. Nimbus adds drafting, segmentation proposals and reply triage on top.
Every published piece keeps reporting in. Comments from every platform land in one queue, triaged: questions get drafted replies grounded in your own content, praise gets a human touch proposed, and complaints are routed to a person — a content bot never answers an angry customer.
Search Console queries, GA4 sessions and per-post platform insights are joined back to the piece that earned them. So 'what worked' is never a feeling — and the next month's strategy proposal cites its evidence.
Your decisions and your results are both training signal — held as rules you can read, confirm and delete, not weights you can't.
Reject three drafts for sounding salesy and the pattern is mined, written down as a tone rule, and shown to you to confirm. Every confirmed rule calibrates every draft after it.
What earned clicks, watch-time and replies feeds the next month’s proposals — which hooks, which lengths, which posting windows. The strategy revises itself, as a diff you approve.
Complaints route to humans. Regulated claims are blocked at draft time. The reply queue never auto-posts — the dial only goes to auto where you set it, channel by channel.
Like Stratus, Nimbus is built on one write pipeline and an audit trail that doubles as the approval queue. These are the rules the contract tests hold.
Every publish, reply and schedule is an action a person approved — or explicitly dialled to auto for that channel. The dial defaults to propose.
Which brief, which strategy slot, which model drafted it, who edited, who approved — attached to the piece, forever.
Amending a draft rejects the original with a reason its author learns from, and publishes yours as your own action.
Approvals double as the history: what was proposed, what changed, what shipped, what it earned.
OAuth grants live in a vault; a missing key fails publishing closed. Revoke a channel and its queue freezes, never leaks.
Search Console rows, GA4 sessions and platform insights are joined back to the piece that earned them — so the next proposal has evidence.
The checker verifies grounding, not the world: “seats 400”, “since 2009”, “re-oil every 6 months” either match the fact book or flag for review. Resolving one is accept, cut, or add the fact.
Renames write 301 redirects with chain collapse. Canonicals, hreflang alternates and the sitemap are generated from the same pages table — they cannot disagree.
Nimbus is ours, built end to end — the strategist, the studio, the video pipeline and the two clips above. We deploy it per brand and shape the strategy around how you already publish. Tell us what your channels look like.
NUAGE OÜ · Tallinn, Estonia · reg. 16039777
ok but rule 2 with kids in the house?? one big piece they will destroy
Honestly — rule 2 survives kids better than five small pieces do: fewer corners, nothing tips. We wrote up the durable-finish options here → fjordpine.co/journal/finishes
Does this work on veneer or only solid wood?
On veneer skip step 3 (the sanding) — the rest applies. The guide covers both, linked in the description.
the corner lamp trick actually changed my whole room 😭
This is exactly the photo we hoped someone would take. Mind if we share it to stories with credit?
my order arrived damaged and support is not answering
routed to support — a complaint is never answered by a content bot