Outsource & co-dev tracking for game studios

Art outsource management for small to midsize teams.

Cyclops is a management workspace made to help game studios navigate co-dev and art outsourcing.

app.cyclopstracking.com/w/ironhold/board

Board

12 tasks · 34 subtasks · 11 approved

Export CSVNew task
GridGalleryKanbanMilestone Organization: AllStatus + FilterFields Save as page
Task
Due
High Poly
Low Poly
Textures
Kael (Hero)
16 Aug
Approved
Approved
Ready for Review
Mira (Hero)
19 Aug
Approved
In Progress
Waiting
Grunt Soldier
31 Aug
In Progress
Waiting
Waiting
Pulse Rifle
10 Aug
Approved
Ready for Review
Waiting
Arc Blade
28 Aug
Ready for Review
Waiting
Waiting
Supply Crate
9 Aug
Approved
Approved
Has Feedback
Fuel Barrel
14 Aug
Approved
Approved
Ready for Review
Wall Terminal
26 Aug
Blocked
Waiting
Waiting
Workbench
11 Sep
Ready to Start
Waiting
Waiting

How it works

The loop runs itself. You watch the board.

01

Create 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.

02

Assign it to a vendor

Each subtask carries one artist, a bid, and a due date. The vendor sees their assignments, and nothing else.

03

Versions come in

An upload flips the status to Ready for Review on its own. No one chases a spreadsheet to say the file landed.

04

Approve or send back

Approval releases the next step from Waiting to Ready. A retake goes back with your markup on the actual frames.

High PolyReady to StartAna A. · due 16 Aug
Low PolyWaitingafter High Poly
TexturesWaitingafter Low Poly
RigWaitingafter Textures

Character: the task type generates the chain. Approve one step, the next goes Ready.

Review

A working surface, not a viewer.

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.

kael_lowpoly_turntable_v003.mp4Kael (Hero) v003 · Low Poly
1 of 3
1920×1080 · 24 fps measured
050100150200250142
0:05.94 / 0:12.00Source · 24 fps
ClearHide markupb pen · e eraser · , . step a frame · space play

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

Build the page you actually need.

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 builder

Producer overview

A production pulse across active work.

Project Producer dashboard PreviewSave page
Waiting on you7versions to review
Overdue2subtasks past due
Logged v estimate84%41d of 49d bid
Breakdown by statusExpanded
30subtasks
Waiting12 · 40%
Approved8 · 27%
Ready for Review5 · 17%
In Progress3 · 10%
Has Feedback1 · 3%
Blocked1 · 3%
Burndown · Vertical SliceWide
Still openPlan said6 behind plan
30 Jun
7 Jul
14 Jul
21 Jul
28 Jul
4 Aug
11 Aug
18 Aug

Automations

Rules you write as a sentence.

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.

Create an automation

Starts when
A version is uploadedversion uploadedA review is submittedreview submittedA status changesstatus changedA blocker clearsblocker clearedA due date is two days awaydue date near
Applies to optional, every filter below must match
Task type matches any ofCharacter Weapon + value
+ condition
Then
Current subtaskSet status toIn Progress
PeopleNotifySelect people
+ action
Reads back as
When a version is uploadedon a Character or Weapon task,set the subtask to Ready for Reviewand notify the reviewers.

Private beta

Currently looking for teams interested in testing.

Beta workspaces are free while we finish. Pricing lands before general availability.

FAQ

Plain answers.

What does it cost?

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.

Can my vendors see each other's work, or my budget?

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.

How is this different from ShotGrid or Jira?

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.

What does setup look like?

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.

Can I rename statuses to match how we work?

Yes. Statuses are your labels over a fixed set of categories, so renaming breaks nothing. Automations and rollups read the category underneath.