# pico.sh

Static sites, blogs and tunnels deployed over SSH — rsync a directory and it is live, with no dashboard and no client to install.


Source: https://www.findhost.app/pico-sh/
Last checked against the provider: 2026-08-14

## Record

### Links

- home: https://pico.sh

### Identity

- founded: unknown
- headcount: unknown
- favorite: unknown
- ownership: unknown
- parent: unknown
- status: active

### Classification

- category: static, vanity-hosting
- whoManagesOs: unknown
- infraContract: unknown
- runsOn: unknown
- cdnFrom: unknown
- useCases: unknown
- audience: unknown
- wikidata: unknown

### Tech stack

- runtimes: unknown
- software: unknown
- specialisation: unknown
- sshAccess: unknown
- managedDatabases: unknown
- gpuCapacity: unknown
- persistentStorage: unknown
- backupsIncluded: unknown

### Deployment

- deployMethods: file-transfer

### Pricing

- pricingModel: unknown
- priceFrom: unknown
- entryPrice: unknown
- priceTo: unknown
- currencies: unknown
- billingPeriods: unknown
- billingTiming: unknown
- exitWithin: unknown
- renewalMultiple: unknown
- freeTier: unknown
- contractMinimum: unknown

### Regions and law

- regions: unknown
- hqCountry: unknown
- gdprDpa: unknown

### Other features

- energyClaim: unknown
- certifications: unknown
- greenWebId: unknown
- domainRegistration: unknown
- dnsHosting: unknown
- emailHosting: unknown
- cdnIncluded: unknown
- testDomain: unknown
- collaboration: none
- staging: unknown

### Support

- supportChannels: unknown
- supportHours: unknown
- supportTiering: unknown

### Automation

- mcpServer: unknown
- cliTool: unknown
- apiAvailable: unknown
- iacSupport: unknown

### Sources

- category: https://pico.sh (read 2026-08-14)
- deployMethods: https://pico.sh (read 2026-08-14)

## Notes

pico.sh is a set of services that all speak SSH and nothing else. Pages hosts a static site pushed with `rsync`, Prose turns markdown sent the same way into a blog, Tuns exposes something running on a laptop at a public address, and Pipe moves data between machines over the same connection. There is no dashboard, no account panel and no tool to install: the client is the SSH already on the machine.

## Worth knowing

The deploy method is the whole point rather than a detail. A workflow that never leaves the terminal is a real preference, and almost nothing else in this register is built for it.

Shell access is left unrecorded rather than answered. SSH is how a file gets there, which is not the same as being given a shell on the machine that serves it, and the row would say the wrong thing either way.

It is small, opinionated and clearly a labour of love. That is worth knowing in both directions before a site that matters is put on it.

---

Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Attributes are recorded, never scored; absent means unknown.
Credit, in full: FindHost, findhost.app, CC BY 4.0