> For the complete documentation index, see [llms.txt](https://peerplays.gitbook.io/peerplays-infrastructure-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peerplays.gitbook.io/peerplays-infrastructure-docs/witnesses/whats-next.md).

# What's Next?

## What's Next?

### 1. Auto-starting your node

Up until this point we have been running the node in the foreground which is fragile and inconvenient. So let's start the node as a service when the system boots up instead.

{% content-ref url="/pages/-Md2MkXvrkFBSVbuYqGp" %}
[Auto-Starting a Node](/peerplays-infrastructure-docs/the-basics/auto-starting-a-node.md)
{% endcontent-ref %}

### 2. Creating a backup node

After that, it would be smart to create a backup server to enable you to make software updates, troubleshoot issues with the node, and otherwise take your node offline without causing service outages.

{% content-ref url="/pages/-Md2Rf3xHUooPwalHNVu" %}
[Backup Servers](/peerplays-infrastructure-docs/the-basics/backup-servers.md)
{% endcontent-ref %}

### 3. Fire up another node :fire:&#x20;

You've got a Witness node. Now you'll need a BOS node. And since you're in the node making mood, how about a SON too?

{% content-ref url="/pages/-MczYO2\_-Q8Qt2S5NyyT" %}
[Bookie Oracle Suite (BOS)](/peerplays-infrastructure-docs/bookie-oracle-suite-bos/introduction-to-bos.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MczY7FmEkaoXcCsVJuM" %}
[Sidechain Operator Nodes (SONs)](/peerplays-infrastructure-docs/sidechain-operator-nodes-sons/installation-guides.md)
{% endcontent-ref %}

### 4. Enable SSL to encrypt your node traffic

If you have a node that is accessible from the internet (for example, an API or Seed node) it would be wise to enable SSL connections to your node.

{% content-ref url="/pages/-MczX\_0A8PUyiFLqnI6r" %}
[Reverse Proxy for Enabling SSL](/peerplays-infrastructure-docs/advanced-topics/reverse-proxy-for-enabling-ssl.md)
{% endcontent-ref %}
