You can deploy Paperclip on an Oracle Cloud ARM Linux VPS through Coolify using Paperclip’s Docker or Compose setup. The critical steps are to connect Coolify to the Oracle server over SSH, allow the traffic required by your setup, use an ARM64-compatible image, persist Paperclip and database data, and route public access through Coolify’s domain and proxy configuration—not by exposing Paperclip’s port directly.
Coolify’s documented host minimums are for running Coolify itself, not a guarantee that one VM can comfortably run Coolify, Paperclip, PostgreSQL, builds, and agents together. Choose capacity for the combined workload and treat Oracle-specific network rules and available ARM shapes as details to confirm in your account and region.
As an Amazon Associate I earn from qualifying purchases.
Choose a deployment layout
There are two decisions to make before configuring the server: whether to use Docker through Coolify or install Paperclip directly, and whether to run Coolify and Paperclip on one machine or separate them.
| Choice | What it means | Trade-off |
|---|---|---|
| Docker through Coolify | Coolify deploys Paperclip’s Docker or Compose configuration. Paperclip’s Docker documentation describes production images for Linux AMD64 and ARM64. Paperclip Docker documentation | Fits Coolify’s Docker workflow and avoids installing Node and pnpm directly on the host. You still need to configure persistent data, image compatibility, and the proxy route. |
| Direct VPS installation | Install Paperclip’s runtime requirements on the host and follow its separate VPS instructions, which include example Nginx and domain setup. Paperclip installation documentation | Uses a host-level installation and its own proxy and upgrade workflow rather than Coolify’s Docker management. |
| One server | Run Coolify and Paperclip resources on the same Oracle VM. | Simpler to operate, but the dashboard, app, database, builds, and agents share CPU, memory, and storage. |
| Separate workload server | Keep Coolify’s control plane apart from the server running Paperclip. | Adds server and connection configuration, but separates resource use. Coolify documents remote deployment servers as an isolation option. Coolify server documentation |
For a straightforward Coolify deployment, use Paperclip’s Docker path. A single server may be practical for a small setup, but do not treat Coolify’s own minimum host specification as a Paperclip workload recommendation.
#1 Best Overall
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKTEC WARRANTY - GMKtec offers a 3-year limited warranty (1 year replacement + 2 years parts replacement) for each mini PC, starting from the date of the purchase effective on all sales starting Oct. 2026. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC
Size and prepare the Oracle ARM server
Coolify documents a minimum of 2 CPU cores, 2 GB RAM, and 10 GB free disk for self-hosting Coolify. Paperclip’s installation documentation separately gives 1 vCPU and 2 GB RAM as a starting point for its VPS path. Neither figure establishes a validated size for running Coolify, Paperclip, PostgreSQL, builds, and agents together on an Oracle ARM VM. Coolify installation requirements · Paperclip installation documentation
- Choose a Linux ARM server with SSH access and enough memory, CPU, and disk for the combined applications and their data.
- Confirm that an ARM-capable server shape and the required capacity are available in your chosen Oracle region. Availability and current pricing are not established here.
- Plan for persistent storage for Paperclip and, if using the full stack, PostgreSQL.
Connect the Oracle ARM server to Coolify
Coolify connects to a deployment server over SSH and performs Docker operations there. Oracle ARM images require extra attention: Coolify’s Oracle guidance says root login is disabled by default and describes either configuring root SSH access with Coolify’s public key or using a non-root account with passwordless sudo. Coolify labels the non-root route experimental in that guidance. Coolify Oracle server guidance
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #2
- Edge2 is equipped with a high-performance SOC - RK3588S2, 8nm lithography process, 8-core 64-bit, 2.25GHz Quad core ARM Cortex-A76 and 1.8GHz Quad core Cortex-A55 CPU Integrated with ARM Mali-G610 MP4 quad-core GPU up to 1GHz，Build-in 6 TOPS Performance NPU
- Edge2 uses the AP6275P Wi-Fi 6 PCIe module supports IEEE 802.11 ax/ac/a/b/g/n and 2T2R. This advanced wireless transceiver module makes data transmission stable and fast
- Edge2 supports 8K, 60fps H.265/VP9 video decoding and 8K, 30fps H.265/H.264 video encoding. In addition, up to 32-channels of 1080P, 30fps decoding or 16-channels of 1080P, 30fps encoding can be done simultaneously
- Quad Display Interfaces: x1 HDMI, x1 USB-C, x2 DSI; Edge2's hardware supports up to four independent displays, however in practice the number of independent displays will be limited by the OS.
- Maker Friendly - Multiple FPC connectors for connecting with accessories and extension. x1 30-pin 0.5mm MIPI-DSI Interface, x1 40-pin 0.5mm MIPI-DSI Interface, x3 30-pin 0.5mm MIPI-CSI Interface, x2 30-pin 0.5mm FPC Connector, x1 7-pin Pogo Pad (USB, UART, 5V) Multiple systems（Android, Ubuntu and many other operating systems）can be installed in a few steps with the built-in OOWOW, easy and fast
- Prepare SSH access. In Oracle and on the VM, configure an SSH account and key that Coolify can use. Follow Coolify’s current Oracle instructions for root-key access or its experimental non-root/passwordless-sudo approach.
- Add the server in Coolify. Use Coolify’s server setup flow to provide the reachable host, SSH user, and key, then validate the connection and Docker access.
- Review both firewall layers. Coolify notes that Oracle ARM servers have a firewall enabled by default. Check the VM’s firewall and Oracle network security rules, then allow only the ports needed for SSH and your Coolify deployment and public proxy setup. The necessary ingress rules depend on the topology; do not assume one universal Oracle rule set.
- Confirm readiness before deploying. Resolve SSH, sudo, Docker, or firewall errors in the server connection check before creating the Paperclip resource.
Deploy Paperclip with an ARM64-compatible Docker setup
Paperclip’s Docker documentation describes a Compose quickstart, with port 3100 as the default, and a full-stack configuration that includes PostgreSQL. It also documents configurable port and data-directory settings. The same documentation says its standard production target publishes Linux AMD64 and ARM64 images; check the exact image and tag used by your deployment rather than assuming every tag or override has the same architecture support. Paperclip Docker documentation
- Create a Docker or Compose resource in Coolify using Paperclip’s documented Docker configuration. Select the full-stack option if you want the documented PostgreSQL-backed setup.
- Verify the image architecture. Make sure the selected production image supports Linux ARM64. If you customize the image, tag, or build configuration, verify that it still targets ARM64.
- Configure persistent storage. Persist Paperclip’s configured data directory. If PostgreSQL is part of the deployment, persist its data directory or volume separately. Confirm the paths and volume mappings against the Compose configuration you actually deploy.
- Set application configuration. Use the documented environment and configuration options for the chosen Paperclip setup, including its configurable port and data directory where needed.
- Keep credentials in secrets. Configure model-provider credentials through Paperclip’s settings or Coolify’s secret/environment configuration as appropriate. Do not commit API keys into a public Compose file or image. Provider availability and adapter support can change, so check Paperclip’s current documentation for the provider you intend to use.
- Deploy and inspect logs. Confirm that the application and, when included, PostgreSQL start successfully before setting up public access.
Route the domain through Coolify instead of exposing port 3100
Paperclip’s VPS guidance says not to expose its application port, 3100 by default, directly to the internet. Its separate VPS walkthrough uses DNS and HTTP/HTTPS for public web access. With Coolify, configure the domain and route through Coolify’s proxy on the server hosting the resource; do not copy the separate Nginx instructions as if they were Coolify’s proxy setup. Paperclip VPS guidance · Coolify server documentation
Rank #3
- Powered by Rockchip RK3576 ARM processor
- Fanless design for silent, reliable 24/7 operation
- Built-in Wi-Fi 5 and Bluetooth
- Compact plug-and-play design for easy deployment
- 64GB eMMC storage with expandable microSD support
- Point the domain’s DNS record to the reachable public address of the server hosting Paperclip.
- In the Coolify resource’s domain or proxy settings, configure the hostname and the application’s internal port according to the deployed configuration.
- Allow the public HTTP/HTTPS traffic required for Coolify’s proxy and certificate setup in the relevant firewall and Oracle network rules.
- After DNS resolves, verify that Coolify serves the Paperclip site over HTTPS and that the app port itself is not publicly reachable.
Back up data and plan upgrades
Persistent volumes keep application and database data separate from a disposable container, but they are not a backup. Before relying on the deployment, establish a backup and restore procedure for Paperclip’s data and PostgreSQL data, if used. The cited deployment guidance identifies persistence needs but does not prescribe an Oracle-specific backup policy, so choose and test a method that fits your storage and recovery requirements.
Recommended Free Tools
For upgrades, use the image and Compose configuration supported by the Paperclip version you intend to run. Preserve the configured volumes, and take a recoverable backup before changing versions or database configuration. Confirm the deployment’s health after the update.
Quick Recap
Common deployment failures
- Coolify cannot connect over SSH: check the selected SSH user, key, root-login configuration, and any sudo requirement against Coolify’s Oracle guidance.
- The server connects but deployment fails: verify Docker access and examine the VM firewall and Oracle network rules for blocked required traffic.
- The image will not run on the VM: check that the selected image/tag supports ARM64 and that a custom build has not changed the target architecture.
- The site is unavailable on its domain: check DNS, the Coolify domain and proxy configuration, the resource’s internal port, and allowed HTTP/HTTPS traffic.
- Data disappears after a redeploy: inspect the Compose-to-Coolify volume mappings and confirm that both application data and database data are persisted at the paths the containers use.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
