01Create a task from a type
A Character generates its subtask chain (High Poly, Low Poly, Textures, Rig) with dependencies wired. First step Ready, the rest Waiting.
Outsource & co-dev tracking for game studios
Cyclops is a management workspace made to help game studios navigate co-dev and art outsourcing.
app.cyclopstracking.com/w/ironhold/board12 tasks · 34 subtasks · 11 approved
How it works
01A Character generates its subtask chain (High Poly, Low Poly, Textures, Rig) with dependencies wired. First step Ready, the rest Waiting.
02Each subtask carries one artist, a bid, and a due date. The vendor sees their assignments, and nothing else.
03An upload flips the status to Ready for Review on its own. No one chases a spreadsheet to say the file landed.
04Approval releases the next step from Waiting to Ready. A retake goes back with your markup on the actual frames.
Ana A. · due 16 Augafter High Polyafter Low Polyafter TexturesCharacter: the task type generates the chain. Approve one step, the next goes Ready.
Review
Markup is vector and sticks to the media, so a drawing is a note in its own right and travels back to the artist with the retake. Video is frame-addressed, with the rate measured when the file opens rather than assumed, and every frame carrying a note is a mark on the ruler.
1920×1080 · 24 fps measured0501001502002501420:05.94 / 0:12.00Source · 24 fps Pen, colour, eraser: the tools a marker pen has. Park on a frame somebody drew on and their marks come back; approving from here releases the next step on the board.
Page builder
Drop modules onto a canvas and configure them: a Breakdown counts subtasks, tasks, estimate days or logged days, splits on any field, and draws as a donut, bars or columns. Save it as a Custom page, or assign it as a role's dashboard.
Page builderA production pulse across active work.
versions to reviewsubtasks past due41d of 49d bid12 · 40%8 · 27%5 · 17%3 · 10%1 · 3%1 · 3%6 behind plan30 Jun7 Jul14 Jul21 Jul28 Jul4 Aug11 Aug18 AugAutomations
Pick what starts it, narrow which work it applies to, choose what happens. No trigger grammar to learn and nothing to script. The rule reads back in the same words you built it from.
A rule can never widen who sees what. Every audience is filtered to people the work is already visible to.
version uploadedA review is submittedreview submittedA status changesstatus changedA blocker clearsblocker clearedA due date is two days awaydue date nearCurrent subtaskSet status toIn ProgressPeopleNotifySelect peoplePrivate beta
Beta workspaces are free while we finish. Pricing lands before general availability.
FAQ
Beta workspaces are free. Pricing lands before general availability. We're testing it during the beta rather than announcing a number we'd have to walk back. Invited vendor artists are free either way; the studio carries the subscription.
No. A vendor organization sees only its own assigned subtasks, and artists never receive bid or cost figures. That isolation is enforced in the query layer. It is a product rule, not a permission checkbox someone can get wrong.
Those assume one company, and getting real value from a pipeline tracker usually assumes a pipeline department. Cyclops is built around the cross-company boundary: outsource planning, bid privacy, submissions, reviews, and approvals that work for a three-person studio.
Define your task types once (Character, Weapon, Prop, Environment) and every new task generates its subtask chain with dependencies wired. No consultants, no onboarding project.
Yes. Statuses are your labels over a fixed set of categories, so renaming breaks nothing. Automations and rollups read the category underneath.