What is Keelson?
This page is under construction.
All Documentation
Introduction
Quickstart
This page is under construction.
Core Concepts
This page is under construction.
Building Apps
Supported App Types
This page is under construction.
Build & Runtime
This page is under construction.
Persistent Storage & SQLite
This page is under construction.
File storage
Section titled “File storage”Your app can save files. Once a write returns, the data is durable — there is no background sync and nothing depends on a local disk that resets on redeploy.
- App data files — files your app names and updates in place (saved state, settings, small caches). Writes are whole-file and take effect immediately; these files are private to your app.
- Media — images, PDFs, and other uploaded or generated media are uploaded to a dedicated store, referenced by an ID, and served over a URL.
For data you read and write on every request, use the managed database instead.
Download Files from Your App
The Keelson CLI does not provide a supported way to place, retrieve, list, or
remove files on a running application’s /data disk.
When users need to retrieve generated output, implement a download endpoint in
the application. Read the file from the application’s managed data source and
return it with appropriate headers, including Content-Type and
Content-Disposition: attachment. Keelson’s normal authentication gate applies
to regular application routes.
Use Keelson Managed SQLite for durable structured data. If the application stores binaries in an external object store, connect to that service from the application. Do not treat a local file as the only authoritative copy.
Read-only retrieval from the persistence store and Console downloads are post-launch backlog items.
Scheduled Jobs (Cron)
This page is under construction.
Configuring with keelson.yaml
This page is under construction.
Deploy
Custom Domains
Keelson will let you serve a deployed app from your own subdomain, such as app.example.com, in addition to the standard public URL Keelson issues for every app.
Planned scope
Section titled “Planned scope”- Plan: Team plan only
- Limit: Up to 10 per tenant in total (one domain per app)
- Supported domains: Subdomains only (
app.example.com). Root domains (apex,example.com) and email domains are out of scope.
When to use it
Section titled “When to use it”- Publish an internal tool under your own company domain
- Give users a clear URL instead of the standard Keelson URL
- Match URLs with an existing internal portal or site
Difference from the public URL
Section titled “Difference from the public URL”A standard public URL is always issued on a successful deploy. A custom domain lets the same app also be reached through your own subdomain. Access-control rules are unchanged: any authentication or IP restriction you have enabled applies to custom-domain traffic as well.
Setup steps (provided when the feature ships)
Section titled “Setup steps (provided when the feature ships)”The concrete setup steps — the DNS records to add, how to verify them, and how TLS certificates are handled — will be documented here when the feature becomes available.
IP Allowlist
This page is under construction.
Access Control
Auth & Login
Members & App Permissions
Workspace
Invite Members
Reference
Keelson Deploy Spec
keelson.yaml
This page is under construction.