How to set up HTTPS with binserve?

Enable TLS in the binserve.json by setting 'enable' to true under 'tls', then provide paths to key.pem and cert.pem files generated with openssl commands, as detailed in the README's TLS section.

Binserve vs Caddy for static file serving?

Binserve offers similar ease with zero-code JSON configuration and better performance via in-memory caching, but Caddy has automatic HTTPS and a larger plugin ecosystem, making it more feature-rich out-of-the-box.

How to use hot reloading in binserve?

Set 'enable_hot_reload' to true in the config section of binserve.json; changes to static files or configuration are detected instantly via the notify library, updating without server downtime.

Can binserve handle dynamic content or APIs?

No, it's designed only for static files and basic Handlebars templating; it lacks support for server-side scripting, databases, or API endpoints, so it's not suitable for dynamic applications.

Is binserve good for high traffic sites?

While fast and secure, the free version misses DDoS protection and rate limiting, so for production traffic, consider the paid binserve+ or augment with external tools like cloudflare.

How to deploy binserve on a Raspberry Pi?

Download the ARM binary from releases, run it to generate configuration, and map routes to static directories; its low memory footprint makes it ideal, as shown in the README with Android examples.

binserve — Fast Static Web Server

What is binserve?

Binserve is a high-performance static web server designed for self-hosters, packaged as a single, portable binary. It serves static files and supports dynamic templating with zero-code setup, prioritizing ease of use, security, and performance through in-memory caching and a Rust-based architecture. It solves the need for a lightweight, production-ready server that is simple to configure and deploy across various platforms.

Target Audience

Self-hosters and developers who need a fast, secure, and easy-to-configure static web server for personal projects, blogs, or static sites generated by tools like Hugo, Jekyll, or Zola. It is also suitable for those deploying on resource-constrained devices like Raspberry Pi or Android phones.

Value Proposition

Developers choose Binserve for its combination of performance, portability, and simplicity—offering built-in TLS, hot reloading, and templating in a single binary with no dependencies. Its unique selling point is the zero-code configuration via a JSON file and efficient in-memory caching that minimizes disk I/O, making it faster than many alternatives.

A fast production-ready static web server with TLS (HTTPS), routing, hot reloading, caching, templating, and security in a single-binary you can set up with zero code.

Use Cases

Best For

Hosting static websites generated by tools like Hugo, Zola, Jekyll, or Hexo with minimal configuration.
Self-hosting personal projects or blogs on low-resource devices such as Raspberry Pi or Android phones.
Deploying production-ready static servers with built-in TLS (HTTPS) support and security hardening against common attacks.
Serving multiple static site directories from a single server instance using flexible routing.
Developing websites with hot reloading for real-time updates to configuration and static files without downtime.
Optimizing static file delivery with client-side caching headers (Cache-Control, Etag) and in-memory caching for speed.

Not Ideal For

Dynamic web applications requiring server-side rendering, database connections, or real-time features like WebSockets.
Enterprises needing built-in DDoS protection, rate limiting, and advanced monitoring without purchasing the paid binserve+ version.
Teams preferring configuration via code or alternative formats like YAML or TOML over JSON files.

Pros & Cons

Pros

Blazing Fast Performance

Leverages Actix-Web, one of the fastest web frameworks, and DashMap for in-memory caching to minimize disk I/O, with benchmarks showing high throughput and low latency.

Extreme Portability

Single binary runs on Windows, Linux, macOS, Android, and Raspberry Pi with no dependencies, demonstrated by gifs in the README showing operation on mobile devices.

Zero-Code Configuration

Setup is automated via a self-explanatory JSON file generated on first run, with hot reloading for real-time updates and secure defaults, requiring no programming for basic deployments.

Built-in Security Hardening

Includes protections against directory traversal and symlink attacks, and uses Rustls for TLS without OpenSSL, ensuring secure connections out-of-the-box.

Cons

Early Development Stage

At version 0.2.0, it may have breaking changes, limited documentation, or undiscovered bugs, which could risk stability for long-term projects.

Limited Templating Engine

Only supports Handlebars for dynamic content, with no option for other templating languages like Jinja2 or Liquid, restricting flexibility for diverse teams.

Advanced Features Behind Paywall

Critical production features like DDoS protection and Prometheus metrics are exclusive to the paid binserve+ version, making the free tier less suitable for high-traffic sites.

What is binserve?

Target Audience

Value Proposition

Use Cases

Best For

Hosting static websites generated by tools like Hugo, Zola, Jekyll, or Hexo with minimal configuration.
Self-hosting personal projects or blogs on low-resource devices such as Raspberry Pi or Android phones.
Deploying production-ready static servers with built-in TLS (HTTPS) support and security hardening against common attacks.
Serving multiple static site directories from a single server instance using flexible routing.
Developing websites with hot reloading for real-time updates to configuration and static files without downtime.
Optimizing static file delivery with client-side caching headers (Cache-Control, Etag) and in-memory caching for speed.

Not Ideal For

Dynamic web applications requiring server-side rendering, database connections, or real-time features like WebSockets.
Enterprises needing built-in DDoS protection, rate limiting, and advanced monitoring without purchasing the paid binserve+ version.
Teams preferring configuration via code or alternative formats like YAML or TOML over JSON files.

Pros & Cons

Pros

Blazing Fast Performance

Leverages Actix-Web, one of the fastest web frameworks, and DashMap for in-memory caching to minimize disk I/O, with benchmarks showing high throughput and low latency.

Extreme Portability

Single binary runs on Windows, Linux, macOS, Android, and Raspberry Pi with no dependencies, demonstrated by gifs in the README showing operation on mobile devices.

Zero-Code Configuration

Setup is automated via a self-explanatory JSON file generated on first run, with hot reloading for real-time updates and secure defaults, requiring no programming for basic deployments.

Built-in Security Hardening

Includes protections against directory traversal and symlink attacks, and uses Rustls for TLS without OpenSSL, ensuring secure connections out-of-the-box.

Cons

Early Development Stage

At version 0.2.0, it may have breaking changes, limited documentation, or undiscovered bugs, which could risk stability for long-term projects.

Limited Templating Engine

Only supports Handlebars for dynamic content, with no option for other templating languages like Jinja2 or Liquid, restricting flexibility for diverse teams.

Advanced Features Behind Paywall

Critical production features like DDoS protection and Prometheus metrics are exclusive to the paid binserve+ version, making the free tier less suitable for high-traffic sites.

binserve

What is binserve?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

binserve

What is binserve?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?