Content Repository Roadmap 2017

Document created by simon.scullion Administrator on Jul 6, 2016Last modified by resplin on Jun 21, 2017
Version 4Show Document
  • View in full screen mode


This roadmap is for the Alfresco Content Repository which is at the core of Alfresco Content Services and Alfresco Community Edition. It does not cover our other open source projects or products, as those teams have their own roadmaps. It communicates what we are currently working on in the calendar year 2017, which corresponds with our Fiscal Year 2018.


Alfresco is an open source company that is committed to open innovation and transparency. This page is a point-in-time snapshot of our current efforts, as our plans are always changing in response to customer input, market evolution and development constraints. You can see our actual progress through our Source Code and our Issue Tracker. Governance of the Content Repository is explained on the page Project Overview: Repository


Unless otherwise noted, In development projects have engineering teams currently assigned. Backlog projects have been scoped and are ready to be started. Keep in mind that in an agile development environment the relative priorities may change throughout the development process. We may not complete all of the items on this list. We might drop a feature because:

  • We need to make room for an effort that we believe will be more valuable to our customers,
  • A feature is difficult or time-consuming to implement, and needs to be deferred or canceled.

For each project, we list whether it will likely be released as open source (OS) as part of Alfresco Community Edition and Alfresco Content Services, be kept proprietary (P) as part of Alfresco Content Services only, or is undecided (U). Our plans around licensing for a specific feature may change at any time before release.



Disclaimer from Our Legal Department:

The information contained herein is intended to outline general product direction and should not be relied upon in making purchasing decisions.

The content is for informational purposes only and may not be incorporated into any contract.

The information presented is not a commitment, promise, or legal obligation to deliver any material, code or functionality.

Any references to the development, release, and timing of any features or functionality described for these products remains at Alfresco’s sole discretion.

Product capabilities, timeframes and features are subject to change and should not be viewed as Alfresco commitments.


Previously Released

This roadmap replaces any previously communicated roadmaps. You can see our previous plans by browsing the documents in the "Roadmap" category. You can see what we accomplished by reading the Release Notes.



Our efforts as a team are organized around two themes:

  • Platform Thinking
    • Robust and stable REST APIs
    • A consistent architecture of the entire Digital Business Platform, encompassing content and process.
  • Running in AWS
    • It needs to be easier to deploy Alfresco in AWS.
    • Our proprietary products will take advantage of advanced AWS features. (P)

Current Projects

OS: Unless otherwise noted, all of the below listed efforts are expected to be open source.

  • Tooling upgrades:
    • Migrating from SVN to Git.
    • Splitting the code base into separate projects.
  • Replacing GhostScript with PDFium
    • This was driven by GhostScript's license change, but PDFium appears to be performing better.
  • Product insight from improved monitoring
    • We need to better understand how our products are used so that we can invest in the right areas.
    • Will replace the web pixel in Community Edition and the Heartbeat in Alfresco Content Services.
    • Make it easy for administrators to know what data is being reported, and to opt-out.
  • Produce a "Reference Deployment" of Alfresco to demonstrate how it should be used in production
    • Based on containers (probably Docker and Kubernetes). See Docker Alfresco Resources?.
    • Likely to replace the packaged installers and
  • Additional REST APIs, especially those needed for the Application Development Framework.
    • Incorporate feedback on the new APIs
    • Audit
    • Avatar
    • Rules
  • Architectural changes for our next major upgrade
  • Stand-alone identity server used across Content Services and Process Services
    • Rework the SSO stack (including the proprietary components like SAML)
  • Replace the embedded Activiti with the stand-alone Activiti
    • Allow people to use the Activiti designers for "workflow", and make it easy to upgrade for full "process services"
  • Improved import / export tooling


Presentations about the Roadmap

Recent presentations about the roadmap include (most recent at the top):