Blog

Unlocking Remote AI: Securely Access Self-Hosted DeepSeek

Unlocking Remote AI: Securely Access Self-Hosted DeepSeek

Why Self-Hosting AI is Great—But Accessing It Isn’t

Self-hosting large language models (LLMs) like DeepSeek is gaining traction for good reasons: privacy, cost efficiency, and performance. But there’s one big hurdle—how do you access your AI remotely without exposing it to the open internet?

Let’s say you’ve got DeepSeek running locally on your workstation. Now you want to query it from your laptop while traveling, connect it to an edge device, or share it securely with a team. Traditional networking options—VPNs, port forwarding, or cloud relays—are either too complex, too slow, or just plain insecure.

Enter RingLink.

RingLink is a decentralized, fully meshed networking solution that allows you to securely connect devices without a centralized server. Unlike traditional P2P tools, RingLink offers direct peer connections when possible but also provides fallback encrypted relays for cases where direct communication is blocked. In this guide, we’ll show you how to:

✅ Set up DeepSeek locally

✅ Create a private RingLink network

Expose DeepSeek over RingLink for remote access

✅ Access your AI from anywhere

DeepSeek R1 Model Hardware Requirements

Model SizeMinimum CPUMin RAM (CPU‑only)Recommended GPU (VRAM)Disk Storage (~GB)Inference Speed – tokens/s (CPU; RTX 4090; A100)
1.5BModern 4‑core CPU (2013+)8 GBRTX 3060 (12 GB, uses ~0.7 GB VRAM)≈1.15 t/s (CPU); **100** t/s (4090); ~80 t/s (A100)
7BModern multi-core CPU (4–6 cores)16 GBRTX 3070 (8 GB, uses ~3.3 GB VRAM)≈4.7~2 t/s (CPU); ~50 t/s (4090); ~40 t/s (A100)
14BHigh-performance CPU (6+ cores)32 GBRTX 3080 (10 GB+, uses ~6.5 GB VRAM)≈9.0~1–2 t/s (CPU); ~60 t/s (4090); ~50 t/s (A100)
32BHigh-performance CPU (8+ cores)64 GBRTX 4090 (24 GB, uses ~14.9 GB VRAM)≈20<1 t/s (CPU); ~30 t/s (4090); ~25 t/s (A100)
70BWorkstation-grade CPU (12+ cores)~128 GB RTX 4090 (24 GB ea., ~32.7 GB total)≈43≪1 t/s (CPU); ~2 t/s (1×4090 with CPU offload); ~10 t/s (A100 80GB)
671BMulti-socket server CPUs (e.g. dual EPYC)≈384–512 GB16× A100 80GB (~1342 GB total VRAM)≈400~5 t/s (CPU only); n/a on single 4090/A100

Step-by-Step Guide

Step 1: Install and Run DeepSeek Locally

1. Install Ollama for Easy Model Management

curl -fsSL https://ollama.com/install.sh | sh

This starts a local DeepSeek server at localhost:11434.

🔍 Troubleshooting: If another service is using 11434, specify a different port:

env OLLAMA_HOST=127.0.0.1:11435 ollama serve

2. Download the DeepSeek Model

ollama pull deepseek-r1:1.5b

Step 2: Install and Set Up RingLink

1. Install RingLink & Join the Network

bash <(curl -s https://assets.ring.link/install.sh) --config-key rl-config-key-{config-key} --user-id {user-id} && ringlink-cli connect {network-id}

2. Verify Connection Status

After installation, check if RingLink is running and connected to the network:

ringlink-cli status

If successfully connected, it should display “Running” and indicate the associated network.

3. Join the Network from Other Devices

Once joined, devices in the network can communicate securely without port forwarding.

🔍 If you experience connection issues:

Step 3: Expose DeepSeek Over RingLink

After setting up your DeepSeek instance, you can expose it over RingLink’s Edge Tunnel (ELB), making it securely accessible without opening public ports.

1. Verify Your DeepSeek Instance

Before exposing your model, ensure it is running correctly:

curl http://localhost:11434/api/generate -d '{
  "model": "deepseek-r1:1.5b",
  "prompt":"Why is the sky blue?"
}'

2. Exposing DeepSeek via RingLink Edge Tunnel (ELB)

Step 1: Create an ELB Instance

1. Visit RingLink ELB Management.

2. Click “Create”, then confirm the ELB configuration.

Step 2: Configure ELB Rules for DeepSeek

1. Find the newly created ELB instance and click “Details”.

2. Set the Source to your DeepSeek server:

3. Assign an external port for public access.

Example:

📌 This is your unique external access point for DeepSeek. Use it to securely connect without exposing your local network.

4. Choose TCP as the protocol and save the configuration.

3. Access DeepSeek Over the Internet

Now that DeepSeek is exposed through RingLink ELB, you can access it securely from any device:

curl http://motionless-advertising.go-elb.com:21434/api/generate -d '{
  "model": "deepseek-r1:1.5b",
  "prompt":"Why is the sky blue?"
}'

📢 Make sure to replace the “motionless-advertising.go-elb.com:21434” with your real ELB endpoint.

💡 Performance Considerations:

Use Cases: Where This Setup Works Best

With this optimized approach, securely accessing your self-hosted DeepSeek AI from anywhere is simple, efficient, and safe.