# Infrastructure overview **Updates May 2023** We base our infrastructure on community best practices. We additionally open source our setup scripts * to make it easy for Ethereum users to setup at home or cloud based validators * to make it easy for our community to audit our practices You can find them here {% embed url="" %} ### Old Sharedstake follows a LEAN startup buy over build methodology and leverages cloud services with high performance and uptime for our ETH2 nodes. To hedge against the risk of synchronized downtime with the majority of cloud hosted ETH2 nodes being on AWS or GCP, we use a German Cloud provider. We currently run a cloud server with 16GB RAM, 8 cores, 150GB Disk space and take monthly backups, and plan to do quarterly resets wherein we sync the beaconDB from scratch to combat bloat we have observed in long running Prysm instances. For ETH1 data we use Alchemy APIs with a fallback on Infura. We use Prysm for our nodes due to: * Several benchmarks demonstrating superior performance * Benchmarks demonstrating less slashing risk and historic slashing incidents than other Validator software * Use of Golang which our engineers are familiar with * Web UI that we can screenshot for our users for transparency * An active and helpful community and discord We've additionally ran our own benchmarks and have tips for others who would choose to run prysm and characteristics of long running Prysm nodes included in the post mortem from an incident where our nodes ran out of disk space. You can read it here: {% embed url="" %} Post mortem - Sep 9 '21 {% endembed %} You can sample Sharedstake validator performance through beaconcha.in by searching for our graffiti `sharedstake.org` Or via this link: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sharedstake.finance/infrastructure-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.