As a Scientist

How can I use CRIMSy?
CRIMSy requires some IT background for installation and maintenance and, in distributed deployments, administrative policies. You therefore should get support by the IT personel of your institution and, in case you plan to be part of a distributed infrastructure, administrative support.
Once CRIMSy is installed in your institution, you simply need to point your web browser to the respective server address.

What does it cost?
CRIMSy is open source, you can use it free of charge. Of course you will need a server to run it, but the initial hardware requirements are moderate (2 CPU cores, 2 GiByte RAM, approx. 20 GByte disk). For test installations, a virtual machine on your desktop computer would be sufficient.

I have found a bug. / I'd like to suggest a feature.
We would be glad to hear from you. You could approach us on GitHub or simply drop us a mail: Please understand that our resources are limited.

Is there any user documentation?
In general, we are aiming at intuitive usability. This should minimize the need for additional documentation. We are currently working to prepare a user handbook covering the most important concepts and use cases.

I want to share data with partners.
Given your partners have access to the same CRIMSy cloud, sharing access is a matter of rights management. It requires only a few clicks to assign or revoke permissions to a specific object to internal or external users or groups.

Is my data safe?
We have implemented several measures to make CRIMSy safe. Ideally, these measures should be complemented by backup and firewalling strategies of the hosting institution. Permanent storage of your data is restricted to your local instance. Our general policy denies any data modification by users from external partner institutions. Many records come with version control, i.e. any modification can be traced and reverted.

As an IT-Administrator

I have been asked to setup CRIMSy. How shall I proceed?
There are two scenarios:

  1. You want to join an existing cloud.
  2. You want to establish a new cloud.
In the first case you need to determine, who is managing the certification authority and the software distribution of this cloud. You need to approach this contact and you will probably receive a link to the software distribution site. This site will guide you through the first steps and point you to our "Configuration & Installation" manual (German only).
In the second case, you need to set up the certification authority and the software distribution site for your cloud. This process is described in our "Administration" manual (German only). After you have set up the certification authority and the software distribution site, you can proceed to configure and install your node.
If you need help, please contact us:

What are the requirements to run a CRIMSy node?
CRIMSy has moderate hardware requirements. You could start with two CPU cores, 2 Gigabytes of RAM, a 20 Gigabytes hard disk and a 10 MBit network connection.

Is CRIMSy secure?
We have put much effort in making CRIMSy secure. We make ample use of encryption, the need-to-know-principle and digital signatures. The source code of CRIMSy has been subject to automated code reviews to discover weaknesses. Individual components of our software stack are isolated by containerization. We have documented the architecture including a risk assessment in our System architecture handbook (German only).

As a Developer

How can I contribute to the development?
CRIMSy is developed on GitHub ( We suggest to get in contact with us:

How can I setup a test instance?
The setup of a test instance and the prerequisites are described in a wiki article on GitHub:

Keys & Certificates

GnuPG public keys
Some of our libraries are signed to guard against tampering. You can use the following public key for signature verification or trusted communication:

The key must be signed with the the eternal key signing key:

CA Certificate
We maintain a private CA for cloud internal purposes. You can download the CA certificate here:

  • CA Certificate (SHA256 fingerprint: ce8ddb3e7e5a7ebdc6c49b6cfcbfcb6397582acdfe63bb7904d31c9f3c3126db)