# Database Networking on Clouddley
Database networking determines how your database communicates with applications and other services. Clouddley provides detailed configurations for **public** and **private** networks, allowing users to use the best option based on their needs. This article covers the key differences and how to select the appropriate database network type on Clouddley.
## Understanding public and private networks
Understanding the differences between public and private networks helps ensure the right database networking choice is made based on security, performance, and accessibility requirements.
### Public Network
A public network allows external access to a database over the Internet, enabling remote connections for external applications and third-party integrations. However, it increases exposure to security threats, requiring strict measures such as IP whitelisting, firewall rules, and encryption. Additionally, internet traffic may introduce latency.
### Private Network
A private network keeps database connections within a secure environment, preventing direct internet access. It supports internal communication, microservices architectures, and enterprise systems with strict security policies. This setup reduces exposure to unauthorised access, improves connection speed and reliability, and enhances access control within a controlled environment.
#### Connecting over the private network
When configuring your database connection over the private network, you can set the host to either the **database name** (for internal connections only) or the **private IP address.**
{% hint style="info" %}
The **database name** is the one you configured when creating your database on Clouddley.
{% endhint %}
The database name in your database’s Overview tab.
## Database Network Settings on Clouddley
Clouddley provides details for both **public** and **private** networks, allowing users to utilise them as needed for their database connections.
Database networking connections tab.
**Choosing the Right Network Type**
Users can use both public and private networks depending on their needs:
* **Public networks** are functional for remote access and integrations.
* **Private networks** offer secure, internal connectivity.
**Using the Public Network**
1. Retrieve the public connection details from Clouddley.
**Using the Private Network**
1. Retrieve private network details from Clouddley.
2. Ensure internal applications and services have the correct network permissions.
3. Use private IP addresses or VPC peering for secure connections.
## Conclusion
Clouddley provides users with public and private network details, ensuring flexibility in database connectivity. Public networks allow external access but require strict security controls, while private networks enhance security by keeping connections internal. By implementing best practices such as access restrictions and encryption, users can maintain a secure and optimised database network.
---
# 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.clouddley.com/databases/extras/database-networking-on-clouddley.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.