DocsPluginsShowcaseReleases
npmStar us on GitHub
overviewcreate-bini-appbini-deploybini-routerbini-envbini-nativebini-serverbini-overlaybini-ssgvite plugins↗hono plugins↗

A native React framework for building cross-platform applications from a single codebase.

Resources

  • Documentation
  • Plugins
  • Showcase
  • Releases

Community

  • GitHub Discussions
  • Reddit
  • Discord
  • LinkedIn

More

  • npm
  • GitHub
  • Issues
  • License

© 2026 Bini Cooperation.

bini-deploy

Official

Zero-config deployment for Bini.js projects - web, desktop, and mobile, all from one CLI.

Overview

bini-deploy scans your project, generates the right hosting configuration for your target platform, and pushes it straight to GitHub. No YAML spelunking, no platform-specific docs to read first.

Features

Web Hosting

Netlify, Vercel, Cloudflare Workers, Deno Deploy. Picks adapter, writes config, wires API routes.

File-based API

Drop files in src/app/api/, bini-deploy scans and mounts each as route with dynamic segments.

Automatic CORS

API routes get permissive CORS headers out of the box on every non-Node adapter.

Native Support

Windows, macOS, Linux, iOS, Android via Tauri with tailored next-step instructions.

Git Built-in

Init repo if needed, sets up identity and auth if missing, commits and pushes.

Smart Diagnostics

Push failures diagnosed - bad credentials, repo not found, or diverged history with accurate recovery.

Install

>_Terminal
$ npm install --save-dev bini-deploy

Quick Start

Run the CLI and answer the prompts:

>_Terminal
$ npx bini-deploy

Step 1 - Choose the target platform

It asks which platform you want to deploy to. Choose Web for any hosting provider:

>_Terminal
◆
Platforms?
◼ Web
◻ Desktop
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm

Step 2 - Choose the hosting provider

If you picked Web, it then asks for the hosting provider:

>_Terminal
◆
Hosting provider?
● Node.js (default)
○ Netlify
○ Vercel
○ Cloudflare Workers
○ Deno Deploy
↑/↓ to navigate • Enter: confirm

Step 3 - Enter your GitHub repository URL

Enter your repository URL (skipped when an origin remote already exists):

>_Terminal
◆
GitHub repository URL?
https://github.com/you/my-app

Step 4 - Choose the branch to push to

By default it pushes to the remote's default branch, falling back to main:

>_Terminal
◆
Branch to push to?
● main (default)
○ + New branch...

Step 5 - Confirm

A confirmation prompt appears before generating files and pushing:

>_Terminal
◆
Generate deployment files and push to GitHub?
●Yes/○No

Step 6 - Commit message

Finally, it asks for a commit message. Press Enter to use the default:

>_Terminal
◆
Commit message (press Enter for the default):
chore: add deployment configuration

Usage

FlagDescription
--platform <type>web, windows, macos, ios, linux, android
--hosting <name>node (default), netlify, vercel, cloudflare, deno (web only)
--repo <url>GitHub repo URL, e.g. https://github.com/you/app
--generate-entry <host>Generate production entry file only
--yes, -ySkip prompts and use flags
--help, -hShow usage information

Examples:

>_Terminal
$ npx bini-deploy --platform web --hosting vercel --repo https://github.com/you/your-app --yes
$ npx bini-deploy --platform windows --repo https://github.com/you/your-app -y
$ npx bini-deploy --generate-entry netlify

Supported Hosting Providers

ProviderRuntimeConfig Generated
Node.js (default)Node (bini-server)None - bini-server handles build/serve
NetlifyEdge Functions (Deno)netlify.toml + netlify/edge-functions/api.ts
VercelNode.js Runtimevercel.json + api/index.ts
Cloudflare WorkersWorkerswrangler.toml + worker.ts
Deno DeployDenoserver/index.ts

API Routes

Any file in src/app/api/ becomes an API route. Nested folders map to URL segments, bracket segments become dynamic params, and spread segments become wildcards:

api
ƒindex.ts
users
ƒindex.ts
ƒ[id].ts
posts
ƒ[...slug].ts
src/app/api/users/[id].ts
export default async function handler(req) {
  const id = new URL(req.url).pathname.split('/').pop();
  return { id, name: 'Ada Lovelace' };
}

Hono Support

If your route file imports from hono, bini-deploy detects it and mounts it as a full Hono app:

src/app/api/hello/route.ts
import { Hono } from 'hono';

const app = new Hono();

app.get('/', (c) => c.json({ message: 'Hello from Hono!' }));
app.post('/', async (c) => {
  const body = await c.req.json();
  return c.json({ received: body });
});

export default app;

How it Works

  1. Scan - scans your src/app/api/ directory for route files
  2. Generate - creates platform-specific entry file and configuration
  3. Clean - removes leftover files from previously selected platform
  4. Push - commits and pushes everything to GitHub
  5. Deploy - hosting platform automatically deploys from GitHub

Git Behavior

  • Existing remote - uses it without modification
  • New projects - adds provided URL as origin
  • Always main - automatically handles branch naming, never pushes to master
  • Git identity - prompts for user.name/user.email once if not set, local only
  • GitHub auth - prompts for username + PAT if push rejected, saves via credential store
  • Remote-ahead recovery - fetches and merges remote history automatically with --allow-unrelated-histories -X ours

Requirements

  • Node.js >= 18
  • Vite >= 6
  • A GitHub repository (created ahead of time)
  • git available on PATH
Was this helpful?
Previouscreate-bini-app
Nextbini-router

On this page

  • Overview
  • Features
  • Install
  • Quick Start
  • Usage
  • Hosting Providers
  • API Routes
  • Hono Support
  • How it Works
  • Git Behavior
  • Requirements
Edit this page on GitHub

bini-deploy

Official

Zero-config deployment for Bini.js projects - web, desktop, and mobile, all from one CLI.

Overview

bini-deploy scans your project, generates the right hosting configuration for your target platform, and pushes it straight to GitHub. No YAML spelunking, no platform-specific docs to read first.

Features

Web Hosting

Netlify, Vercel, Cloudflare Workers, Deno Deploy. Picks adapter, writes config, wires API routes.

File-based API

Drop files in src/app/api/, bini-deploy scans and mounts each as route with dynamic segments.

Automatic CORS

API routes get permissive CORS headers out of the box on every non-Node adapter.

Native Support

Windows, macOS, Linux, iOS, Android via Tauri with tailored next-step instructions.

Git Built-in

Init repo if needed, sets up identity and auth if missing, commits and pushes.

Smart Diagnostics

Push failures diagnosed - bad credentials, repo not found, or diverged history with accurate recovery.

Install

>_Terminal
$ npm install --save-dev bini-deploy

Quick Start

Run the CLI and answer the prompts:

>_Terminal
$ npx bini-deploy

Step 1 - Choose the target platform

It asks which platform you want to deploy to. Choose Web for any hosting provider:

>_Terminal
◆
Platforms?
◼ Web
◻ Desktop
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm

Step 2 - Choose the hosting provider

If you picked Web, it then asks for the hosting provider:

>_Terminal
◆
Hosting provider?
● Node.js (default)
○ Netlify
○ Vercel
○ Cloudflare Workers
○ Deno Deploy
↑/↓ to navigate • Enter: confirm

Step 3 - Enter your GitHub repository URL

Enter your repository URL (skipped when an origin remote already exists):

>_Terminal
◆
GitHub repository URL?
https://github.com/you/my-app

Step 4 - Choose the branch to push to

By default it pushes to the remote's default branch, falling back to main:

>_Terminal
◆
Branch to push to?
● main (default)
○ + New branch...

Step 5 - Confirm

A confirmation prompt appears before generating files and pushing:

>_Terminal
◆
Generate deployment files and push to GitHub?
●Yes/○No

Step 6 - Commit message

Finally, it asks for a commit message. Press Enter to use the default:

>_Terminal
◆
Commit message (press Enter for the default):
chore: add deployment configuration

Usage

FlagDescription
--platform <type>web, windows, macos, ios, linux, android
--hosting <name>node (default), netlify, vercel, cloudflare, deno (web only)
--repo <url>GitHub repo URL, e.g. https://github.com/you/app
--generate-entry <host>Generate production entry file only
--yes, -ySkip prompts and use flags
--help, -hShow usage information

Examples:

>_Terminal
$ npx bini-deploy --platform web --hosting vercel --repo https://github.com/you/your-app --yes
$ npx bini-deploy --platform windows --repo https://github.com/you/your-app -y
$ npx bini-deploy --generate-entry netlify

Supported Hosting Providers

ProviderRuntimeConfig Generated
Node.js (default)Node (bini-server)None - bini-server handles build/serve
NetlifyEdge Functions (Deno)netlify.toml + netlify/edge-functions/api.ts
VercelNode.js Runtimevercel.json + api/index.ts
Cloudflare WorkersWorkerswrangler.toml + worker.ts
Deno DeployDenoserver/index.ts

API Routes

Any file in src/app/api/ becomes an API route. Nested folders map to URL segments, bracket segments become dynamic params, and spread segments become wildcards:

api
ƒindex.ts
users
ƒindex.ts
ƒ[id].ts
posts
ƒ[...slug].ts
src/app/api/users/[id].ts
export default async function handler(req) {
  const id = new URL(req.url).pathname.split('/').pop();
  return { id, name: 'Ada Lovelace' };
}

Hono Support

If your route file imports from hono, bini-deploy detects it and mounts it as a full Hono app:

src/app/api/hello/route.ts
import { Hono } from 'hono';

const app = new Hono();

app.get('/', (c) => c.json({ message: 'Hello from Hono!' }));
app.post('/', async (c) => {
  const body = await c.req.json();
  return c.json({ received: body });
});

export default app;

How it Works

  1. Scan - scans your src/app/api/ directory for route files
  2. Generate - creates platform-specific entry file and configuration
  3. Clean - removes leftover files from previously selected platform
  4. Push - commits and pushes everything to GitHub
  5. Deploy - hosting platform automatically deploys from GitHub

Git Behavior

  • Existing remote - uses it without modification
  • New projects - adds provided URL as origin
  • Always main - automatically handles branch naming, never pushes to master
  • Git identity - prompts for user.name/user.email once if not set, local only
  • GitHub auth - prompts for username + PAT if push rejected, saves via credential store
  • Remote-ahead recovery - fetches and merges remote history automatically with --allow-unrelated-histories -X ours

Requirements

  • Node.js >= 18
  • Vite >= 6
  • A GitHub repository (created ahead of time)
  • git available on PATH
Was this helpful?
Previouscreate-bini-app
Nextbini-router

On this page

  • Overview
  • Features
  • Install
  • Quick Start
  • Usage
  • Hosting Providers
  • API Routes
  • Hono Support
  • How it Works
  • Git Behavior
  • Requirements
Edit this page on GitHub