How it fits together
Each product works alone. Together they stop you doing things twice.
A rule written once in a design becomes the value your game reads. A stream becomes clips and posts. A show's setlist becomes a stream's run sheet. These are the flows the products run today.
The map
How the software connects
Making comes first, then shipping, then reaching people. Each number is a link the products have today.
Canon into design
A game cites the characters, places and events of its OnlyLore universe instead of copying them, and is told when a citation no longer matches.
A score for the game
A game links to an Ensemblis project for its score, where songs are written as adaptive music.
Design into config
Parameters and catalogues are bound to a publishing project's config. They are changed in the design, and the console shows them as managed by that game. A protected environment waits for a person to release the change.
A game's news into marketing
A brand linked to a game on the platform sees its builds, config releases and crash fixes as things worth saying, and gets the Steam tools and store numbers.
Marketing and design, both ways
Features shipped, milestones and approved assets reach the brand as pipeline sources. Players' feedback goes back into the game's design, and a store brief comes out of it.
Shows into streams
A show's setlist becomes the stream's run sheet, each song a marker, and each song a clip waiting as a draft when the stream ends.
Every link is optional. Each product works on its own, and a connection is something you turn on. See every product
Streamers and creators
A stream becomes clips and posts
Go live once and Marketing does the rest of the week's work, up to the point a person should look at it. A pipeline picks the moments, cuts them, and writes the posts. It stops at a draft or an approval unless you choose otherwise.
- Stream onceFrom OBS to our relay, which sends it on to YouTube and Twitch and keeps a recording.
- Find the momentsChat spikes, viewer jumps, and every "Clip that" pressed during the stream.
- Cut the clipsWidescreen and vertical, with captions and a thumbnail, into the library.
- Write the postsAI drafts in the brand's voice, one form of the post per channel.
- Approve and measureA person approves. Numbers come back after an hour, a day, a week and a month.
Game studios
A game from design to players
Numbers live in the design. Bind them to your publishing project and the test environment follows the design, while production waits for a person to release the change. When a build or a fix goes out, the brand that markets the game can see it.
Design
- Game DesignerRules and numbersEach number is a parameter, written once.
Test
- PublishingConfig in testBound parameters land in your test environment.
Release
- PublishingCompare and promoteSee what differs, choose what goes, and release it to production.
Players
- Your gameSign-in, config, lobbies, savesOne API, with no new build for a config change.
Tell people
- MarketingBuilds and fixes become newsReleases and crash fixes show up as things worth saying.
Publishers
A publisher's brands, sharing what makes sense
A central team sets up channels, mailboxes, ad accounts and pipelines once, and the brands in its org use them. A brand can follow a shared pipeline and override a step, say with its own subreddit, and getting its own account later changes nothing else. Sharing stays inside one org, and a borrower never sees the credentials.
The central team
- The publisher's brandHolds the channels, mailboxes, ad accounts and pipelines, and shares what it chooses.
The org's brands
- A game's brandStreams on the shared YouTube and follows the shared pipeline.
- Another game's brandKeeps the shared YouTube, and posts to its own subreddit.
What stays true
- A brand's own account winsNetwork by network, with no parent brand to work around.
- Work stays with its brandA stream, post or campaign belongs to the brand that made it.
Bands
A band's show, from songs to clips
Write each song once, build the show, and let ShowSync lay it out in Ableton Live. If you stream it through Marketing, the setlist runs the stream, and each song is cut as a clip for you to look at afterwards.
- EnsemblisSongs, onceSections, tempo, cues and what changes on each part of the rig.
- EnsemblisA showAn ordered list of songs, each as written or rearranged for the night.
- ShowSyncLive Sets builtOn the Tracks computer and at front of house, cached for offline gigs.
- MarketingThe stream followsThe setlist is the run sheet, and each song a marker.
- MarketingA clip of each songWaiting in the library as a draft. Covers are skipped.
Writers and game masters
A world that stays one world
OnlyLore holds the canon. A game cites it instead of keeping its own copy, and an assistant reads it through scoped access, so everybody answers from the same place. A world needs no game to be useful, either.
- OnlyLoreWrite the worldCharacters, eras, factions and events, with collaborators as editors or readers.
- Game DesignerA game cites itRules and catalogues point at canon rather than retelling it.
- Your AI assistantAn assistant reads itScoped access, so it answers from what you wrote.
Working with us
Publishing for Small Indie Studios
GreenMind Media is a game publishing company for small independent studios. We take on the infrastructure and business overhead of shipping a game so your team can stay focused on making it.
Screenshots on this page show made-up sample data.