Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Smallweb

Smallweb is a new take on self-hosting. The goal is to make it as easy as possible to host your own apps. To achieve this, it uses a "file-based hosting" approach: every subfolder in your smallweb folder becomes a unique subdomain.

Smallweb is obsessed with scaling down. No dev server or a build is required, and you don't even need to care about deployment. You can just write a single file, hit save, and voila! Your app is live.

Example

Let's say I want to self-host my own drawing app.

First, I'll create a folder for my app:

mkdir-p~/smallweb/draw

Then, I'll create a main.ts file in that folder:

// ~/smallweb/draw/main.tsimport{Excalidraw}from"jsr:@smallweb/excalidraw@0.9.1";constexcalidraw=newExcalidraw({rootDir: "./data"});exportdefaultexcalidraw;

And voila! No need to run a single command, your website is already available at https://draw.<your-domain>! And each time the drawing is modified, it get automatically persited to ~/smallweb/draw/data/drawing.json.

Tired of it ? Just run rm -rf ~/smallweb/draw and it's like it never existed.

Try it out

Leave me a message at excalidraw.smallweb.club, and then go create your own website from vscode.smallweb.club! Also feel free to join our discord to ask any question or just hang out with us!

Application structure

Smallweb tries to keep it's api as simple as possible. The only requirement is to have a default export in a main.ts file at the root of your website folder

// ~/smallweb/example/main.tsexportdefault{fetch: (request: Request)=>{returnnewResponse("Handling request!");},run: (_args: string[])=>{console.log("Running command!");},email: (_msg: ReadableStream)=>{console.log("Received email!");},}

You can invoke:

the fetch function by send a request to https://example.<your-domain>
the run function by running smallweb run example or ssh example@<your-domain>
the email function by sending an email to example!<your-domain>

Of course, it is super easy to hook these functions to a web framweork like hono or a cli framework like commander.

// ~/smallweb/hono/main.tsimport{Hono}from'npm:hono'constapp=newHono()app.get('/',(c)=>c.text('Hono!'))exportdefaultapp

And if your app folder does not contain a main.ts file, smallweb statically serves the content of the folder instead.

How it works

Smallweb is distributed as a single golang binary, and use deno as it's runtime. It uses a serverless architecture, where deno workers are spawned on-demand to handle requests.

If your pet project as no traffic, it won't consume any resources. And if it gets too popular, there is no lock-in, you can easily move to a more traditional hosting provider.

Smallweb leverages deno sandboxing capabilities to isolate each website from each other: then only have access to their own files, and can't interfere with the rest of the system.

Name		Name	Last commit message	Last commit date
.devcontainer		.devcontainer
.github		.github
.vscode		.vscode
example		example
internal		internal
schemas		schemas
.envrc		.envrc
.gitignore		.gitignore
.golangci.yml		.golangci.yml
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Caddyfile		Caddyfile
Dockerfile		Dockerfile
LICENSE.md		LICENSE.md
README.md		README.md
compose.yaml		compose.yaml
docker-entrypoint.sh		docker-entrypoint.sh
go.mod		go.mod
go.sum		go.sum
goreleaser.yaml		goreleaser.yaml
main.go		main.go

Name		Name	Last commit message	Last commit date
.devcontainer		.devcontainer
.github		.github
.vscode		.vscode
example		example
internal		internal
schemas		schemas
.envrc		.envrc
.gitignore		.gitignore
.golangci.yml		.golangci.yml
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Caddyfile		Caddyfile
Dockerfile		Dockerfile
LICENSE.md		LICENSE.md
README.md		README.md
compose.yaml		compose.yaml
docker-entrypoint.sh		docker-entrypoint.sh
go.mod		go.mod
go.sum		go.sum
goreleaser.yaml		goreleaser.yaml
main.go		main.go

Name		Name	Last commit message	Last commit date
.devcontainer		.devcontainer
.github		.github
.vscode		.vscode
example		example
internal		internal
schemas		schemas
.envrc		.envrc
.gitignore		.gitignore
.golangci.yml		.golangci.yml
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Caddyfile		Caddyfile
Dockerfile		Dockerfile
LICENSE.md		LICENSE.md
README.md		README.md
compose.yaml		compose.yaml
docker-entrypoint.sh		docker-entrypoint.sh
go.mod		go.mod
go.sum		go.sum
goreleaser.yaml		goreleaser.yaml
main.go		main.go

Name		Name	Last commit message	Last commit date
.devcontainer		.devcontainer
.github		.github
.vscode		.vscode
example		example
internal		internal
schemas		schemas
.envrc		.envrc
.gitignore		.gitignore
.golangci.yml		.golangci.yml
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Caddyfile		Caddyfile
Dockerfile		Dockerfile
LICENSE.md		LICENSE.md
README.md		README.md
compose.yaml		compose.yaml
docker-entrypoint.sh		docker-entrypoint.sh
go.mod		go.mod
go.sum		go.sum
goreleaser.yaml		goreleaser.yaml
main.go		main.go

Name		Name	Last commit message	Last commit date
.devcontainer		.devcontainer
.github		.github
.vscode		.vscode
example		example
internal		internal
schemas		schemas
.envrc		.envrc
.gitignore		.gitignore
.golangci.yml		.golangci.yml
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Caddyfile		Caddyfile
Dockerfile		Dockerfile
LICENSE.md		LICENSE.md
README.md		README.md
compose.yaml		compose.yaml
docker-entrypoint.sh		docker-entrypoint.sh
go.mod		go.mod
go.sum		go.sum
goreleaser.yaml		goreleaser.yaml
main.go		main.go

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Smallweb

Example

Try it out

Application structure

How it works

About

Resources

Contributing

Stars

Watchers

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Smallweb

Example

Try it out

Application structure

How it works

About

Resources

Contributing

Stars

Watchers

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Smallweb

Example

Try it out

Application structure

How it works

About

Resources

Contributing

Stars

Watchers

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Smallweb

Example

Try it out

Application structure

How it works

About

Resources

Contributing

Stars