FAQ
Questions developers ask about BASRUN
This is a static mock site. Answers describe intended product behavior.
What is BASRUN?
BASRUN is a hosted runtime concept for running Basil packages in the cloud via schedules (cron), webhooks (HTTP triggers), or REST-style routing.
What is a Basil package?
A Basil package is the deployable unit — a single `.basil` file or a ZIP containing multiple files and assets — plus configuration like mode and entry point.
Can I deploy a single file or do I need a ZIP?
Both are intended. Single-file deployments are great for small jobs. ZIP packages are better when you have multiple modules, templates, or static assets.
Does scheduling support cron expressions and timezones?
Cron expressions are the core model. Timezone support is expected; exact behavior may vary by plan and is subject to change.
How do webhooks map to functions?
In webhook mode, an HTTP request triggers a configured entry point function (for example, `webhook.basil`). BASRUN passes the request method, path, headers, and body.
How does REST routing work?
In REST mode, a router entry point handles multiple paths under a base URL (for example, `/api/your-pkg/*`). You can implement simple routing in Basil, or use a helper library when available.
What are the sandboxing and resource limits?
BASRUN is intended to run packages in an isolated sandbox with CPU/memory/time limits. Exact limits depend on the plan and may change over time.
How are secrets handled?
Secrets are expected to be stored encrypted and injected into the runtime as environment variables or scoped secret values. Never hardcode secrets in source.
Will BASRUN support GitHub deployments?
GitHub-based deployment is a common workflow (link repo → pick path/branch → deploy). This UI mock references it as a planned option.
Is there an approval process for public endpoints?
Some platforms require additional checks for public webhooks or higher quotas. BASRUN may include plan-based approvals to reduce abuse and improve reliability.
What are the Free tier limits?
The Free tier is intended for learning and light usage (limited runs, lower resource caps). Limits are subject to change as the product evolves.
How does pricing work (tokens)?
Usage is measured in tokens (a simplified unit representing compute + I/O). You can buy token bundles or use pay-as-you-go depending on the plan.
What logs and observability are available?
Per-run logs, recent history, basic metrics (error rate, last/next run), and token usage are intended. Deeper tracing can be added later.
How can I get support?
During the preview phase, support is provided via the community forums and GitHub discussions. Priority support for production users is planned.