What's New at Sliplane: Faster Builds, SSH Access, APIs, and Dedicated Power

At Sliplane, we're building the simplest way to run your Dockerized apps in production. No Kubernetes, no YAML jungles, just containers that work. We've been quietly shipping a bunch of new features lately, and it's time to share what's new under the hood.

Whether you're building a SaaS, self-hosting open source tools, or deploying internal workloads, these updates are all about speed, flexibility, and control.

🚀 API Access (Finally!)

You can now programmatically manage your Sliplane resources via our new API.

Create servers, deploy containers, trigger builds. All from your own scripts, CI pipelines, or internal tools. We've documented everything over at ctrl.sliplane.io.

Use case:

• Automate spinning up preview environments.
• Build your own control dashboard.
• Integrate with tools like GitLab CI, GitHub Actions, or n8n.

Anything missing? Let us know and we will add it!

🔐 SSH Access to Services

You can now SSH directly into your running services. Debug live issues, inspect logs, or mess with your database, all without setting up custom access.

$ ssh -p 22222 service_id@server_id.sliplane.app

You are now connected to service_id running in shell /bin/sh
/your-service #

Docs here → docs.sliplane.io/services/ssh

Use case:

• Run a one-off DB query in a Postgres container
• Inspect a failing app in production
• Tail logs the old-school way (not sure why you would do this, but hey, it's there)

🧾 Multiline .env Support

Secrets that span multiple lines (like private keys, JSON blobs, or certs) now work out of the box in your service environment variables.

Use case:

• Load a full OpenAI service account key
• Add a private RSA key to your app
• Store full JSON config in a single var

⚡️ Faster Builds

Our build servers now run with 32 GB RAM and 4 dedicated CPU cores. Your Docker builds are now faster, especially for larger apps with more dependencies.

Under the hood, we've made more caching improvements and optimized deployment times. The average deploy will be 5-10 seconds faster!

Use case:

• Build Rust, Node.js, or Python apps with complex dependency trees
• Run multi-stage Docker builds with less waiting
• Shave seconds (or minutes) off CI/CD pipelines

🧱 Dedicated Instances

Need raw horsepower? You can now spin up dedicated servers with up to:

• 48 vCPU
• 192 GB RAM

Use case:

• Host AI inference backends (even CPU-bound ones)
• Run high-traffic databases or internal analytics tools
• Power multi-user apps with heavy concurrency

💤 Pause Services (and Save Money)

You can now pause individual services when you're not using them.

⚠️ Note: The server itself will still run and be billed. The container is stopped, which is especially useful for dev environments.

Use case:

• Pause staging or test environments over the weekend
• Temporarily shut down less-used side projects
• Reduce load without deleting data

🔧 Better Reliability

We've made a ton of behind-the-scenes improvements: faster provisioning, more resilient networking, smarter build retries, and improved service health monitoring.

You probably won't notice. And that's the point.

PS: Has any cloud provider ever said that they haven't become more reliable?

🧭 What's Next?

We're not done. Here's what's coming soon:

• Private networks between servers
• Better Docker Compose Support
• More one-click templates
• And... some fun surprises 👀

💬 We'd Love Your Feedback

Tried these new features? Have an idea we should build next? Just reply here, or message us via our chat widget in the bottom right corner. We're always listening.

Cheers,

Jonas, Co-Founder Sliplane