We took a step forward on our road to innovation and the result of it is here: Its name is Octo.

Octo stands for “Open Core for Technology Orchestration”. It is a web-based orchestration layer that displays information from our other applications, including TD/OMS, in an organized and visual way.

Octo is the framework that allows us to bind all our applications together. From it, you can access all information from our applications TD/OMS and Gravity. 

Octo is still in Beta

Octo is very new. It can only do a couple of things at the moment. However, some very nice features are available for TD/OMS users. You can also play with our Demo Kanban engine that we will roll out in Milestone 3.

Octo is a cloud-based application, and you can reach the public Octo server here: https://octo.remainsoftware.com

Please expect some hiccups when using the Octo server. It is a work in progress. You can file issues and enhancement requests at https://helpdesk.remainsoftware.com

TD/OMS Dashboard

The Octo TD/OMS Dashboard shows analytical information about the state of your TD/OMS server. It will signal warnings like missing source and problematic transfers. It contains trend analysis charts to show how your DevOps is improving over time.

Please read the internal wiki documentation (login required) to find out how to plug in your TD/OMS.

TD/OMS Work Management

Octo allows you to see all the tasks and requests in TD/OMS.

To configure Octo to work together with your TD/OMS, please follow the instructions on our wiki

The following features are available:

  • Create Task and Request Filters
  • Show the Dashbord
  • Change basic Information
  • Ratify a task or a request
  • Deep link your task or request (e.g. from your issue tracking tool)




Octo comes with a Kanban tool that shows tasks and assignments in an organized way, from to-dos, to work in progress, testing, and completed. You can easily move tasks from one column to another, delete them, and sort them at your convenience.

At the moment the Kanban is operating against an internal database. We are going to hook in TD/OMS in milestone 3.