Roadmap: where Otter has been, and where we see it going.

Otter is by no means "feature complete", and although the software works great for our users today, we're actively working on making it even better. This roadmap page is a bit rough, but it should show you which changes we plan on making in releases to come.

We decide on what changes to make to Otter based on a number of factors, the largest of which is user feature requests. If there's anything you think Otter should do — or should do better — please contact us and let us know.

Version 2

The central theme of v2 is provisioning your servers and managing configuration, this means you can manage them automatically, without ever needing to log-in to a command prompt. You can define reusable sets of configuration called roles, and then scale your infrastructure by simply assigning these roles to any number of servers.

To see specific planned changes, you can view our open Otter issues in our issue tracker.

Already Released:

  • Otter 2.0 - Updated UI, Inedo SDK, Configuration Versioning

Otter 2.1 Plan:

We have a bunch of exciting things in the works for Otter 2.1, check back regularly for updates as we announce what features are on the horizon.

Version 1

  • Otter 1.7 - Enhanced LDAP Directory and Advanced Templating
  • Otter 1.6 - Server Packages, Resource Pools, Role Dependencies
  • Otter 1.5 - List and Map Indexers and New extensions
  • Otter 1.4 - Agentless Windows servers, variables improvements, OtterScript features, new APIs
  • Otter 1.3 - Inedo Den, a community and extension portal
  • Otter 1.2 - infrastructure export, import, and sync
  • Otter 1.1 - Linux/SSH agents, Git-based Rafts
  • Otter 1.0 - initial, production-ready release

The central theme of v1 is disruption. Otter v1 will make your Windows servers a first-class DevOps citizen, and bring visibility of server configuration to everyone in your IT organization, not just those fluent in proprietary, Ruby-based DSLs.

v1 is fully supported; bug fixes will continue to be shipped in the 1.7 release, and we will continue to maintain earlier v1 releases to resolve any critical or security issues discovered for users who cannot yet upgrade to 1.7