# Combining SNO with Satellite Node Operator **URL:** \ **Category:** Developer Discussions\ **Tags:** storagenode, multiple-nodes, satellites\ **Created:** [September 10, 2020, 10:42pm UTC](https://forum.storj.io/t/combining-sno-with-satellite-node-operator/9081 "2020-09-10T22:42:48Z")\ **Posts on this page:** 1\ **Showing post:** 30
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [October 21, 2020, 7:42am UTC](https://forum.storj.io/t/combining-sno-with-satellite-node-operator/9081/30 "2020-10-21T07:42:45Z")
Yes, but not distributed, as you suggest. If serious, I think that you can just run a satellite, but it should be provisioned differently from storagenode. However, you can try to run them both, but you will need a HA setup with Kubernetes or Docker swarm cluster and Ceph under the hood. Don’t forget about HA for networking and power supply. > [@Distributed architecture for SNOs for high availability of storage nodes](https://forum.storj.io/t/distributed-architecture-for-snos-for-high-availability-of-storage-nodes/6538/3): > > The replication should be on other level - storage, not the application. We should not invent the wheel - you can use a Gluster or Cepf for that, which are robust these days and have a long history of development, it will be more reliable than introduce a replication on SN level, because we do not have an implementation of replication anymore. Your node can only spread pieces across the network during the Graceful Exit. I don’t think you want that in case of compute failure. For the compute f… --- _[View the full topic](https://forum.storj.io/t/combining-sno-with-satellite-node-operator/9081)._