Roadmap
Acadex is still in Early Access. Some parts of the system are already in place. Others are being developed, tested, or deliberately left open until we understand the real need better. This roadmap shows where things currently stand. It is not a list of promises with invented deadlines.
These are parts of Acadex that already form the foundation of the product.
Work with bibliographic research data
Acadex can work with data on publications, researchers, authorship, and citations. You can use that data to investigate research profiles, publication histories, citation relationships, and connections between researchers and publications.
Compare researchers and research profiles
Acadex can compare researchers, groups, and publication records. That includes questions such as: where publication histories overlap; how research profiles differ; which publications connect researchers; and how activity changes over time.
Trace citations
Acadex can examine citation relationships in both directions: Which publications does a paper cite? And which later publications cite it? The underlying bibliographic records remain inspectable.
Work with documents
You can upload documents such as papers, preprints, or other research material and work directly with their content. Acadex can use the document itself as part of the research context rather than relying only on bibliographic metadata.
Persistent research context
Acadex can retain useful context between conversations. Saved memories can help avoid explaining the same research context repeatedly. You can review, correct, and delete saved information.
Watchlists
Researchers and publications that matter to you can be saved to watchlists. Watchlists provide a persistent place for following research objects without having to reconstruct the same collection every time.
Traceable answers
Where Acadex uses bibliographic records to produce an answer, comparison, or calculation, the underlying sources remain visible. Traceability is part of the basic product rather than a premium add-on.
Multiple model providers
Acadex is designed so that the research system is not permanently tied to a single language-model provider. Different providers can be integrated and used according to the task and account configuration. Provider availability does not mean that every provider processes data from every account.
These are areas we are actively working on or preparing for production use.
Researcher
We are preparing the paid Researcher plan for people who use Acadex regularly. Researcher will include a recurring monthly credit allowance for the more processing-intensive parts of Acadex. The exact price and allowance will be based on real usage and operating costs rather than an arbitrary message limit.
Institutional processing profiles
Institutional accounts need more control over which external model providers and processing paths can be used. We are developing processing profiles that can define requirements such as: permitted provider; endpoint; processing region; available models; retention controls; and permitted provider features; A profile will only be offered as an approved institutional route once it has actually been implemented and verified.
European model-processing routes
We are evaluating and implementing European processing paths for supported model providers where the underlying infrastructure and contractual conditions allow it. A provider advertising EU processing does not automatically make that route available in Acadex. We verify the complete processing path first.
Monitoring and operational visibility
We are improving production monitoring and observability. Acadex is currently monitored administratively, but we want failures and unusual system conditions to become easier to detect and investigate automatically. We will describe those controls as implemented only once they are actually running.
Backup and recovery procedures
The protection of primary application data is being formalised further. This includes defined PostgreSQL backup intervals, retention periods, and regular restore testing. The exact operational values will be documented once they are established in production.
These capabilities are relevant to where Acadex is going, but they are not generally available today.
Multi-factor authentication for Acadex accounts
Administrative systems already use multi-factor authentication. MFA for individual Acadex user accounts is planned separately.
Institutional single sign-on
Institutional authentication through systems such as Shibboleth, DFN-AAI, or comparable SSO infrastructure is not yet generally available. It becomes particularly relevant where institutions want to manage larger numbers of personal Acadex accounts centrally.
Stronger institutional administration
Institutional use will require more than simply assigning several subscriptions. We expect this area to include clearer seat management, institutional configuration, usage allocation, and administration of permitted processing profiles.
More structured notifications
Watchlists become more useful when Acadex can surface meaningful changes without requiring users to check them manually. We are working toward better notification options while avoiding notification systems designed simply to increase engagement.
Additional credit options
We may introduce optional additional credit packages for Researcher users who temporarily need more capacity. Running out of credits will not trigger an automatic purchase. If additional credits are introduced, their price, amount, and validity will be shown before purchase.
Some ideas are worth investigating without pretending that we have already decided to build them.
Better ways to understand research fields over time
Bibliographic data can reveal how research areas develop, split, converge, and influence one another. We are exploring ways to make those changes easier to investigate without reducing them to a single metric.
Deeper relationship analysis
Publications, researchers, institutions, and citations form networks. We want to explore ways of making those relationships easier to inspect while keeping the underlying evidence visible.
More useful research workflows around documents
Working with one document is only one part of research. We are exploring how Acadex can work more naturally across collections of documents, bibliographic records, and ongoing research context.
We do not want to add functionality simply because other AI products have it. Some things may be technically possible and still not make Acadex better for research. We are particularly cautious about features that would:
Engagement optimisation
Features that optimise for time spent inside the product rather than useful work.
Anything that hides the trail
Features that would make research less traceable.
Behavioural collection
Anything requiring unnecessary collection of user behaviour.
Obscured provenance
Anything that would obscure which model or data source was actually involved.
Judgement by proxy
Features that would replace a judgement researchers should make themselves.
We will add dates when we have enough confidence to make them useful. Until then, a status such as In development or Planned says more than an arbitrary quarter attached to uncertain work. The roadmap can change as we learn more from real use. When something becomes available, the product and documentation should reflect that actual state.
Especially during Early Access, concrete requirements are useful. If a missing capability blocks a real research workflow or institutional deployment, tell us. That is more useful to us than a generic feature vote.
We are a small team in Osnabrück. Pick the route that fits and you will reach someone who can actually answer.
Seats for a group or department, payment by invoice, a data processing agreement, or a walkthrough with your team.
Talk to usSomething is not working, or you want to know whether Acadex can do the thing you have in mind.
Get supportPress, partnerships, or a note about how well your field is covered. That last one is genuinely useful to us.
Send a message