# Prodigy Roadmap

**URL:** <https://support.prodi.gy/t/prodigy-roadmap/32>\
**Category:** Uncategorized\
**Tags:** enhancement, meta\
**Created:** [September 13, 2017, 10:00pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32 "2017-09-13T22:00:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [September 13, 2017, 10:00pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/1 "2017-09-13T22:00:00Z")

</div>

This roadmap should give you an overview of what’s next for Prodigy and other ideas worth exploring. Feel free to ask questions, or submit requests and suggestions in the comments.

### [**📋 See here for the changelog.**](https://prodi.gy/docs/changelog)

* * *

### Recipes, Components and Interfaces

- ✅ `v1.5.0` [manual image annotation](https://support.prodi.gy/t/demo-fully-manual-image-annotation-interface/215): image segments (square and polygon shapes)
- ✅ `v1.5.0` allow plugging in recipes, databases and loaders via Python entry points
- ✅ `v1.5.0` validate stream using JSON schemas before starting the server and while Prodigy is running, and output detailed messages if tasks don’t have the expected format
- add built-in solutions for [pseudo-rehearsal](https://explosion.ai/blog/pseudo-rehearsal-catastrophic-forgetting) and data augmentation
- add more features to manual image annotation interface: editing shapes, undo/redo, fully tested touch screen support and more

### Models

- add support for [sense2vec](https://github.com/explosion/sense2vec) models
- 🔜 built-in wrappers for scikit-learn, Pytorch and TensorFlow / Keras: those will be available via spaCy’s machine learning library [Thinc](https://github.com/explosion/thinc). You can already test the experimental PyTorch integration in the latest release.

### Prodigy Annotation Manager

**Status:** ✳️ active development  
**Public beta:** September 2018 (earlier for existing Prodigy users)

- set up large annotation projects with multiple annotators, perform quality control and check concordance
- **add-on product** and library that integrates with Prodigy, orchestrates recipes and tasks, and manages your cluster
- admin console for settings, statistics and annotator management
- full data privacy, support for internal and external networks

### Database and Corpus Management

**Status:** ✴️ planning

- separate **open-source** library for managing and reconciling annotation layers
- integrates with seamlessly with Prodigy – but can also be used standalone!
- out-of-the-box support for training spaCy models and adapters for other libraries
- possible add-on: web UI for viewing data and annotations

### Documentation

- ✅ `v1.4.0` “[Prodigy Cookbook](https://prodi.gy/docs/cookbook)” with quick solutions for various problems
- produce more **end-to-end video tutorials** like our [text classification with Prodigy](https://www.youtube.com/watch?v=5di0KlKl0fE) video
  - Improving spaCy’s NER model on your data
  - Manual NER annotation
  - Image segmentation and object detection
  - A/B evaluation
  - Data curation and manual annotation (e.g. image selection and preference)

---

<div class="post-metadata">

**Author:** ![yusun](https://avatars.discourse-cdn.com/v4/letter/y/7993a0/32.png) [@yusun](https://support.prodi.gy/u/yusun)\
**Post date:** [June 20, 2018, 7:46pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/4 "2018-06-20T19:46:08Z")

</div>

When could we expect the release of the built-in wrappers for Pytorch and TensorFlow/Keras?

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [June 21, 2018, 8:13am UTC](https://support.prodi.gy/t/prodigy-roadmap/32/5 "2018-06-21T08:13:29Z")

</div>

> [@yusun](#):
>
> When could we expect the release of the built-in wrappers for Pytorch and TensorFlow/Keras?

In a recent release of Thinc, we quietly shipped the first version of a [PyTorch wrapper](https://github.com/explosion/thinc/pull/61) so we can start testing it 🙂 The wrappers will be open-source so they can evolve and be updated quickly. It also means that Prodigy won't have to ship with a bunch of super specific code that may have to change often, and it allows you to reuse them across applications, without having to depend on Prodigy.

---

<div class="post-metadata">

**Author:** ![idealley](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/idealley/32/290_2.png) [@idealley](https://support.prodi.gy/u/idealley)\
**Post date:** [June 22, 2018, 9:13pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/6 "2018-06-22T21:13:04Z")

</div>

For the “Prodigy Annotation Manager” do you need help? Beta testing, developing some parts? I am asking because we are launching an annotation project for our medical data. I have tested prodigy by adding two entity, it all worked out. I can generate my models etc. Therefore I am ready to move to the next step 😉

Sam

---

<div class="post-metadata">

**Author:** ![plusepsilon](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/plusepsilon/32/49_2.png) [@plusepsilon](https://support.prodi.gy/u/plusepsilon)\
**Post date:** [June 25, 2018, 9:44pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/7 "2018-06-25T21:44:06Z")

</div>

I’ll be happy to early test the annotation manager as well.

We have a multiple Prodigy set-up using `pm2` but it’s very clunky 🙂

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [June 26, 2018, 8:46am UTC](https://support.prodi.gy/t/prodigy-roadmap/32/8 "2018-06-26T08:46:31Z")

</div>

@idealley @plusepsilon Thanks a lot! We’re not quite yet at a stage where it’s ready to be tested by others – but there’ll definitely be an alpha/beta program exclusively for existing users 😊

---

<div class="post-metadata">

**Author:** ![steve](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@steve](https://support.prodi.gy/u/steve)\
**Post date:** [August 20, 2018, 11:07pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/9 "2018-08-20T23:07:14Z")

</div>

@ines Sorry to keep bugging you about the Annotation Manager (really excited!), but do you have a sense of how close you are to a private beta (a week, a month)? I’ve been putting off building an internal solution, but we have a use case that likely can’t wait until the end of September.

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [August 27, 2018, 3:43pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/10 "2018-08-27T15:43:47Z")

</div>

@steve Ah, sorry, I totally missed your comment! We actually _just_ started our Prodigy Annotation Manager sprint to finish up the app, and we’d obviously love to get it out to people as soon as possible. We’ll hopefully have an update and an announcement to make about the results this week!

However, I still wouldn’t be comfortable making any promises at this point, especially if you have to meet your deadlines. So in the meantime, you might want to check out @andy’s [open-source multi-user extension](https://github.com/ahalterman/multiuser_prodigy). The annotation manager will be fully compatible with Prodigy’s existing database formats, so you’ll always be able to make the switch later.

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [September 7, 2018, 3:22pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/11 "2018-09-07T15:22:17Z")

</div>

@idealley @plusepsilon @steve Just posted an update here 🎉

> [@sparkles Prodigy Annotation Manager Update // Prodigy Scale // Prodigy Teams](https://support.prodi.gy/t/prodigy-annotation-manager-update-prodigy-scale/805):
>
> Many of you have been asking about how to scale your Prodigy projects – including how to manage more annotators, how to keep multiple feeds running, and how to make sure your annotators stay in agreement. These are challenging problems that are outside of the scope of the [Prodigy](https://prodi.gy) software itself, so we've always planned an extension product that helps you use Prodigy in larger products. We've been quietly working away on this for some time, so we're excited to finally announce our progress! The …

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [November 13, 2018, 6:19pm UTC](https://support.prodi.gy/t/prodigy-roadmap/32/12 "2018-11-13T18:19:51Z")

</div>


