Create your own imaging modules using the programming language of your choice, as we use Docker, or build on others’ work.
Combine private and public image processing modules into customized solutions. Automate the workflows for increased productivity and reproducibility.
Save valuable research time by not reinventing code. Share work with your team or with the community. Work from anywhere using any device.
Mobilize the coding power of developers around the world to address your research problem.
Reveal your skills and develop solutions to real research problems.
It is a simple idea that drives us: Imaging Specialists are handling up to five different software solutions in order to create one good workflow. That workflow runs locally somewhere and is not shared. Imaging student with no prior coding knowledge are thus struggling with their image processing tasks. We want to change that! APEER is an initiative started by ZEISS to offer customizable solutions to the microscopy community.
There will always be a free version - APEER Core. Due to our users’ higher demand in storage and processing power, we are working on a subscription based Pro version, which will be rolled out soon.
APEER is fully funded and supported by ZEISS. This does not mean it is only for ZEISS customers using ZEISS microscopes. APEER has modules to read most file formats, including ZEISS’ own CZI format. That said, if you have a ZEISS microscope running ZEN 2.6 or later, you can trigger workflows directly from ZEN instead of logging on to the platform from apeer.com and uploading files manually. The integration with ZEISS microscopes will get strong in future based on your feedback.
Your intellectual property rights are fully protected while using APEER. This includes all your data (images and results), modules and workflows on the platform. For statistical purposes as well as for improving the platform services for our customers, we may occasionally use anonymized data.
Data security is a top priority for us. We utilize latest security mechanisms provided by Microsoft Azure. Your files can only be accessed by you and whoever you have chosen to share the data with. As long as your code is in a private module, only technical support staff can have access to it if need be.
The computing resources are configurable. Current setup is 12 GB of RAM and guaranteed 1 CPU and maximum of 3 CPU units based on the current system utilization. The same parameters are used for GPU units. Our GPU unit is NVIDIATesla K80. You have 100 GB of storage capacity with the free version of APEER. If you want to accelerate your computation you can create modules which run on GPU.
To streamline the compatibility of APEER modules we settled on using OME-TIFF as a default recommended file format. Our goal is to make it as easy as possible for you to create custom workflows – therefore we want to have all modules supporting the OME-TIFF file format so that they can work together in a reliable way.
We are working hard on optimizing the Module building experience. It's our goal to make it much easier and faster to build a Module, even without programing skills. This feature will also allow you to get existing code much faster on APEER making it possible to combine it with other Modules.
You are now able to view and download module results directly when running a Workflow. All file outputs and even non-file outputs can be previewed while your workflow is still running. This makes it possible to check intermediate results without waiting for the whole workflow to finish and will make it much easier and faster to optimize your workflow parameters to fit to your needs.
“APEER is just the solution we need. Actually, if APEER wouldn't exist, we would probably have to develop it on our own.”
“As microscopists, we built the platform we always wished for. A platform that lets any researcher customize and automate image processing tasks regardless of their coding skills.”
These teams are using APEER to their advantage.