{% extends "core/site_base.html" %} {% block tabtitle %}Contact - Simmate{% endblock %} {% block body %}

Frequently Asked Questions

{% simmate_setting "website.show_finances" as SHOW_FINANCES %}
Privacy

You can install Simmate locally to run private workflows or run them on your private server. But as far as the public website goes: no, you can not make any of your results private. In the spirit of building a community that openly shares chemistry data, everything in our public website will remain openly accessible to everyone.
{% if SHOW_FINANCES %}

We aim to be as transparent as possible with our finances. This is because, as an open collective, we want users to know that the science & our community comes first - and that all funds going through Simmate are fairly distributed. A public ledger might be suprising, but it is by no means revolutionary. Simmate uses pseudonymity -- where all transactions are public, but user identities are not. This is exactly how many cryptocurrencies operate, including the most popular currencies like Bitcoin and Ethereum.
{% endif %}

  • Email & Name: only your email and (if it's available) your name are stored. We will never send you promotional emails or newsletters.
  • {% if SHOW_FINANCES %}
  • Country/State: this is only required for purchases made on Simmate, and we only need this information for tax purposes. We are required to collect this by "Know your Customer" regulations, but if there's ever the option, we will gladly remove this from our data collection.
  • {% endif %}
  • Website Traffic: every new page visit is logged so that we can go back and scale cloud resources appropriately, see what features users are most interested in, and utilize stats for grants/funding.
{% if SHOW_FINANCES %}
Finances

It is pay-as-you-go for workflow submissions. Per-workflow cost varies, and price can often not be calculated until you provide your inputs. This is because input parameters (such as the molecule/structure you provide) can influence compute time, and in turn the price. So set up your workflow run, and you will be able to reviece + accept the workflow quote before submission. Also, you can drastically reduce or eliminate these costs by running tasks on your own compute.

You need to set up and run a Simmate Worker on your personal computer or wherever your hardware is located. Keep in mind that USDC collateral is required to start a worker, but your full balance is redeemable as soon as you stop your worker. The full guide is located in our documentation here.

You can earn USDC by configuring a Simmate Worker on your computer and linking it to a community worker pool (such as a pool specific to small DFT jobs). Keep in mind that USDC collateral is required to start a worker, but your full balance is redeemable as soon as you stop your worker. The full guide is located in our documentation here.
{% endif %}

Simmate is completely free. If you decide to download and host your own server, your team may want to use a cloud provider like DigitalOcean, AWS, or GCP. These extra cloud-hosting features are 100% optional because every component for Simmate is built on free and open-source software. As a rough estimate, a minimal setup within a cloud provider will be ~$50/month the for k8s setup plus postgres db.
Licensing

Simmate is open-sourced under the BSD-3 License. This permits commercial use, modification, distribution, and private use - but still has limitations, such as where you can use the Simmate name. Read the specifics here.

Everything. Whatever you see on the website, you can also do in a local/private setup. In fact, you can in many cases do more with a local setup, because locally you can integrate additional datasets that we are not able to include in the public website.
Community

You can contribute in many ways: improving documentation, proposing new features, building new apps, and more. Start a discussion or open an issue on Github if you want to contribute features or code. For anything else, feel free to send us an email. See our Contact page for more info.

Yes, please send suggestions! Send us an email or make a post on Github. Any feedback is welcome, and we'll do our best to prioritize new components.
{% endblock %}