001
A continuously operating content system for payments.
Turn everything your company knows into ideas, authority and demand.
Juno is a continuously operating content system that combines a dreaming engine, content agents, company memory and GEO/AEO intelligence to continuously discover, research, produce and improve the content that moves business.
For payments product, content and communications teams.
002 · The knowledge gap
Your best content is already inside the company. It just cannot find its way out.
The sharpest customer language ends inside a call recording.
BURIEDThe proof behind the launch lives across six documents.
SCATTEREDProduct experts repeat the same explanation in private.
INVISIBLEThe calendar asks for topics before it asks what matters.
BACKWARDSResearch starts again every time the assignment changes.
AGAINAI visibility gaps sit inside a dashboard instead of becoming work.
STRANDEDA useful claim loses its source on the way to the draft.
UNPROVENBrand voice is remembered differently by every writer.
DRIFTThe final edit teaches the next draft nothing.
FORGOTTENOne strong story becomes ten rushed rewrites.
DILUTEDApproval arrives after the context has left the room.
LATEThe market cannot cite expertise it cannot see.
MISSINGA blank box strands company expertise inside the business. Juno carries the context into the work, where customers and answer engines can use it.
003 · The dreaming engine
The next idea is already hiding in the work.
Juno keeps company knowledge and market signals in motion. It finds the questions customers are already asking, the proof that deserves a wider audience and the visibility gaps worth closing.
002
Catch the thought before it behaves.
Speak it, type it or bring the raw note. Juno keeps the useful language intact long enough to turn it into a question, a claim or a direction worth researching.003
Dream with evidence nearby.
The dreaming engine finds tensions, unanswered questions and unexpected connections inside company knowledge and current market signals. Ideas arrive with a reason to exist.004
Find demand before choosing a deliverable.
Customer questions, product changes and visibility gaps reveal what the market needs to understand. Juno ranks the opportunity before deciding what should be written.005
Research until the argument has bones.
Juno plans multiple lines of inquiry, searches the web and retrieves evidence section by section. Sources stay close enough to inspect, challenge and reuse.006
Turn visibility gaps into work.
GEO/AEO intelligence identifies the questions and entities the company should own. Juno turns those gaps into cited briefs and content; compatible imports and Profound connections remain bounded by the configured access available.007
Keep the proof beside the prose.
Claims retain their sources, warnings and version history. A sentence can travel through the system without losing the route back to what made it defensible.008
Send the job to the right specialist.
Each content agent owns a different research, structure, draft and review path. People direct the assignment and approve the work; the system handles the route between those decisions.009
Let the final edit improve the next beginning.
Juno keeps ideas, research, useful versions and confirmed lessons in memory. The system gets better at finding and making the work without inventing a voice the company never had.004 · The operating loop
One system. Every piece knows what happens next.
Discover the opportunity. Research what is true. Send the job through the right specialist. Prove the claims, learn from the final edit and use the result to decide what the system should make next.
Long-form work keeps research visible instead of treating it as a pre-draft errand.
Research can safely fail or be unavailable. Juno says so. Export changes with the workflow.
005 · Company memory
Company memory, visible inside the work.
RAG brings the relevant material forward. The knowledge graph keeps products, people, claims and relationships coherent. Brand voice shapes the draft. Citations preserve the route back. Inspect the same memory moving through Brief, Research and Draft.
Case study brief
A payment can be paid and still unfinished
Show why authorization, capture and settlement must be read as separate clocks—and what a product team should do when the customer only sees one of them.
The same material does not need the same blank box. It needs a visible route from the question to the evidence, from the evidence to the sentence, and from the sentence back to the person who must approve it.
Juno changes the working surface when the assignment changes. The route remains inspectable.
006 · Ten specialist content agents
Different jobs need different operators.
Each agent can run its own research, structure, draft and review path against the same company memory. People set the job, shape the direction and approve the work. The system handles everything between those decisions.
01ApolloBlog
Own the question customers and answer engines keep asking.
02HephaestusTechnical writing
Make product decisions legible enough to earn technical trust.
03AthenaCase studies
Turn customer change into proof the next buyer can use.
04HermesPress releases
Find the news and give the market a reason to care now.
05ThemisRFP responses
Turn company knowledge into precise, defensible deal answers.
06PoseidonIn-depth
Own a difficult idea before the category settles for a simpler one.
07MnemosyneResearch papers
Establish a position that can survive contact with the evidence.
08ClioEbooks
Build durable authority around an argument worth keeping.
09IrisCarousels
Carry one sharp argument through a sequence people will finish.
10DionysusTurn internal expertise into a point of view people remember.
007 · Intelligence and proof
Public fixture pending · method previewMake what the company knows visible—and citable.
GEO/AEO intelligence shows where the company is absent, misunderstood or impossible to cite. Juno turns those gaps into grounded work, keeps the evidence attached and leaves judgement with the person who must stand behind the words.
PROOF.01
See the visibility gap
Start with the questions, entities and claims the market cannot currently find or cite.
PROOF.02
See where the answer came from
Open the material behind the draft and trace every important claim back to its evidence.
PROOF.03
See what changed
Compare the revision, the review and the source that caused the work to move.
PROOF.04
See what to improve next
Carry confirmed lessons and new visibility signals into the next brief instead of starting over.
008 · For teams
Move the work that moves the business.
Launches, category authority, answer-engine visibility and deal velocity are different outcomes. Juno gives every team a place to begin without splitting company knowledge into four separate systems.
Product marketing
Turn product change, customer proof and market demand into launches that give sales something useful to carry forward.
Content
Build a compounding body of cited work that earns search visibility, answer-engine presence and category authority.
PR and communications
Find the news inside the business, support it with proof and keep the story moving after announcement day.
Field and solutions
Turn distributed product knowledge into deal answers, technical explanations and evidence buyers can trust.
009 · The Journal · 24 published essays
What continuous operation looks like.
The Journal is the operating model made visible: company knowledge and current signals become cited ideas, drafts and published arguments on a continuing cadence. Not another folder of prompts. A body of work that keeps growing.
A payment integration begins where the API ends
Provider changes that pass request tests can still alter webhook meaning and break settlement reconciliation, leaving a compiling integration with corrupted financial history.
Journal.02Give every payment failure a seed
Uncontrolled clocks, random choices and event ordering let a repaired test pass for the wrong reason, while the production race remains intact.
Journal.03The fastest payment API can still lose the benchmark
Without eligibility gates, a weighted score can allow duplicate effects or false success to be offset by milliseconds and disappear inside a respectable total.
010 · Product status
What runs now. What gets connected next.
The product already discovers ideas, retrieves company knowledge, researches, writes, reviews and keeps the work. The next step is connecting those capabilities into longer-running, approved content operations.
Available now
- Feature 01Dreaming and idea generation
- Feature 02Company-memory retrieval
- Feature 0310 specialist content workflows
- Feature 04Citation-aware web research
- Feature 05Voice, review, versions and export
- Feature 06Blog GEO/AEO guidance
- Feature 07Ideas, Library and Journal
- Feature 08No-account local saves
Profound remains qualified: it requires user access and an operator-configured server-side Profound-compatible MCP gateway, not native hosted OAuth. Juno's bounded import and safety envelope are verified. Live workspace-data compatibility therefore remains unverified.
Coming soon
- Feature 01Shared context across workflows
- Feature 02Approved-step writing agents
- Feature 03Connected content pipelines
- Feature 04Live visibility connectors
- Feature 05Learning from edits and performance
- Feature 06Large-set personalisation
- Feature 07Campaigns across channels
011 · Questions
The part where we answer the awkward questions.
Q.001What is Juno built on?
Juno is a modern web application built with Next.js, React and strict TypeScript. It combines purpose-built writing surfaces, local-first drafts, voice input, bounded web research, source-aware review and export. It can read PDF, DOCX, XLSX, CSV, Markdown and text files. Optional services remain separately configured, so the writing experience does not depend on an account or a shared Writing Desk runtime.
Q.002Does it work with Claude and ChatGPT?
Yes, on the eight writing surfaces where an external model helps. Review what will be shared, then copy one complete packet and open Claude or ChatGPT with the brief, research pack, citations, outline, current draft, quality checks and surface-specific inputs intact. Both providers receive the same packet, so choosing a model does not quietly leave half the work behind. RFP and Carousel intentionally stay inside Juno. ChatGPT launch and response are verified with a harmless browser fixture. Claude reaches the expected sign-in boundary; logged-in Claude interpretation remains unverified in this environment.
Q.003Who is Juno built for?
Payments product, content and communications teams. Juno is most useful when the team knows the subject but needs a better way to turn that knowledge into clear writing.
Q.004Do I need an account?
Not for now. Juno runs without an account while user profiles are disabled. Profiles are coming later; the writing experience works without waiting for them.
Q.005What can I write?
Blogs, technical writing, case studies, press releases, RFP responses, in-depth pieces, research papers, ebooks, carousels and LinkedIn posts. Those ten jobs each get their own way in.
Q.006Why ten workflows?
A press release and a research paper share plenty of nouns. They do not share a process. Juno keeps the useful parts consistent and lets each kind of writing behave like itself.
Q.007Can I talk to Juno?
Yes. Voice dictation appears across all ten writing briefs, Ideas, chat and rewrite controls. Talk through the thought and Juno turns it into editable text. Browser support still decides whether the microphone control appears.
Q.008How deep does the research go?
Past the first page of results. Juno plans different lines of inquiry, searches across the web, builds a research pack and retrieves evidence again while long sections are being written. Methods inspired by Stanford's STORM research help it look from more than one angle; citations keep the route back to the source visible.
Q.009What makes Juno different from a general writing tool?
A large payments corpus, ten purpose-built writing paths, Ideas, voice, deep research and review rules that change with the work. Juno begins with payment systems and the piece you are making, rather than asking one heroic prompt to discover both.
Q.010How does Juno help with AEO?
Blog writing already uses an AEO frame for extractable answers, useful question-shaped sections, entity context, comparisons and FAQs. Upload a compatible export from any AEO tool, paste a Profound JSON export, or choose Connect Profound (requires Profound access and a configured connector). This uses an operator-configured server-side Profound-compatible MCP gateway, not native hosted OAuth. Deeper parity with Jasper's AEO tooling and more native AEO-platform connectors are coming soon.
Q.011Where are the agents?
In the roadmap. Juno can research, structure, draft and review today, but it does not send autonomous agents off to approve or publish work. Agents may later move pieces through steps a person has approved.
Q.012Will Juno publish for me?
No. Juno helps you make and export the writing. The publish button belongs somewhere else, under the hand of someone who means to press it.
Q.013Where is the work saved?
In this version, your work is saved locally in Juno, with a separate data mirror where the environment has one configured. User profiles are disabled for now, so there is no account dashboard. Profiles and account-based continuity are coming later.
Q.014What can I export?
The useful form of the work: Markdown for long-form drafts, structured output where the format needs it, and the full context manifest for Claude or ChatGPT. An RFP table should leave as a table. A carousel should remember that it has slides.
Q.015What is Juno definitely not?
Juno does not move money, pretend every sentence is true or publish by itself. It helps payments teams think, research and write. That is already a fairly full day.
012 · Begin
What should Juno move next?
Start with an opportunity, a visibility gap or the job already sitting on your desk. Juno brings company memory, research and the right specialist agent. You keep the direction and the final word.
Juno is a continuously operating content system for payments product, content and communications teams.









