English
Blinko Hosting
Capture notes, ideas, and tasks quickly in a private personal knowledge space.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Blinko’s official links and original website
Blinko Website
More
Tech
- Docker image
- blinkospace/blinko:latest
- Default port
- 1111
- Database
- postgres
How Blinko works
Blinko provides a quick-entry stream for short thoughts and a note area for longer material. Users capture text, tasks, links, and supported attachments without first designing a deep folder structure. Tags, search, and different note views then help turn the running collection into a personal knowledge workspace.
The distinction between a quick “blinko” and a fuller note supports two writing rhythms: record an idea immediately, or develop a durable document with more structure. Selected content can be shared through public links, while account access keeps the main workspace private.
Key Blinko features
Markdown-based writing keeps notes portable and supports headings, lists, code, links, and other structured text. Tags and search provide flexible retrieval, while task items let users keep lightweight actions beside the knowledge that created them.
Blinko also documents optional AI-assisted search and processing. Those functions require a compatible external model or API configuration; they are not the same as the core note system and should not be presented as included model usage. Public sharing can expose selected notes without opening the whole account. The compact workflow keeps rapid capture and later review inside the same browser workspace.
Who uses Blinko
Individuals use Blinko for fleeting ideas, project notes, reading references, personal tasks, code snippets, and work journals. It is useful when capture speed matters more than a rigid hierarchy and when the same private workspace should hold both short entries and developed notes.
Blinko is less suitable for formal document approval, large multi-department wikis, or project management with advanced dependencies. Optional AI features also depend on external services and may introduce separate cost, privacy, and availability considerations.
Self-hosting Blinko: requirements and cost
Resource use is shaped by note count, attachments, search indexing, active users, public shares, and optional AI-related processing. PostgreSQL stores accounts, notes, tags, tasks, and configuration. AvaHost provisions PostgreSQL with the application, but the database remains unmanaged.
Blinko has no separate software charge for the hosted core application, and the database-adjusted minimum is Plan 2 at €5. Blinko hosting provides one-click setup, a personal domain, automated HTTPS, automatic application updates, and scheduled backups. No AI model subscription, API allowance, or inference hardware is included; optional AI features require a compatible external provider configured by the user.
F.A.Q
Blinko starts at €5 on Plan 2 after including capacity for its PostgreSQL service. The Blinko plan includes one-click setup, a custom domain, automated HTTPS, application updates, and scheduled backups. Note volume, attachments, search activity, active users, public shares, and any externally configured AI processing influence whether more resources are needed.
AvaHost deploys PostgreSQL beside Blinko and connects the application to it automatically. Notes, tags, tasks, users, and configuration depend on that database, while supported attachments use persistent application storage. PostgreSQL is included but unmanaged, so both data areas should remain aligned during updates, exports, and recovery.
A custom domain can be attached to the Blinko workspace, with automated HTTPS applied after the DNS record points to AvaHost. After the address changes, verify sign-in, public shares, uploaded files, browser bookmarks, and any external integrations that may still refer to the original platform hostname.
No model subscription, API usage allowance, or inference hardware is included with the AvaHost app plan. Blinko’s optional AI functions require a compatible external provider and user-supplied credentials. Provider charges, model behaviour, response speed, and data handling remain separate, so the core note workspace should be evaluated independently of those optional features.