BlinkHost Developer Documentation
Build confidently. Know exactly what production is running.
Task-focused guides for developers and agencies—from the first browser preview to backend modules, managed data, immutable deployment, production diagnostics, and rollback.
Choose the outcome you need
Browse by product
Delivery
Deploy your first BlinkHost project
Create a project, verify it in the browser, and promote one immutable production release.
Deploy and roll back immutable releases
Promote a verified artifact once and recover by selecting a prior artifact.
Troubleshoot a failed deployment or production release
Use immutable release evidence to distinguish upload, build, promotion, routing, and health failures.
Availability, support and recovery boundaries
Check service health, report production impact and distinguish rollback from data recovery.
Support, incidents and service evidence
Know which service signals are public, how incidents are communicated and which commitments require a contract.
How trusted builds and releases work
Follow source from an approved snapshot to a verifiable production release.
Use BlinkHost Field Notes
Find reviewed technical deep dives, field guides, dispatches, labs, references and downloadable tools.
Teams Agencies
Set up an agency workspace
Organize client projects and teammate access without crossing workspace boundaries.
Agency handoff, client access and billing
Separate client access, transfer ownership deliberately and record every resource that needs a new owner.
Team roles and client handoff checklist
Assign the least access required and transfer every source, delivery, data and billing dependency deliberately.
Frontend
Use the browser IDE and preview
Edit the complete project and connect browser-local frontend work to isolated backend preview modules.
Troubleshoot WebContainer and LiveStack preview
Separate device-side frontend startup from remote module build, session and resource failures.
Upload and use project assets
Add validated images, fonts, audio and video to the IDE while using the workspace's shared storage allowance.
Accessibility, device and global-use guidance
Choose a workable browser, understand current language and region limits, and request help with an access barrier.
Backend Modules
Build a Rust backend module
Compile Rust source with the managed offline toolchain and BlinkHost SDK 1.0.
Build a Go backend module
Compile Go source with TinyGo and the BlinkHost SDK 1.0 host contract.
Evaluate a Python backend module
Use the managed CPython-WASI pipeline while accounting for Preview compatibility limits.
Choose a backend module language
Understand available runtimes and their compatibility boundaries.
Run functions from events and schedules
Configure reliable background, event, and scheduled function runs.
Backend module SDK 1.0 reference
Use the versioned Rust, Go, and Python guest interfaces for the blinkhost-wasi-1 host ABI.
Troubleshoot backend module builds and runtime failures
Separate source, toolchain, Wasm validation, capability-policy, and runtime errors.
Call external services over HTTPS
Use guarded backend HTTPS, understand policy and resource limits, and reconcile uncertain external operations.
Source Control
Build with Idam
Describe an idea, follow implementation and review a private preview. Learn about saved conversations, voice, files, credits and the task API.
Connect your AI to BlinkHost
Connect an AI assistant, choose project access, manage permissions and hand a Git revision to BlinkHost.
Connections and current research
Connect workspace tools with reviewed permissions. Use paid-plan live search, monthly workspace allowances and saved sources.
Project evidence
Understand the source revision, relationships, coverage and verification records Idam uses for a project.
BlinkHost capabilities used by Idam
Read supported application types, available operations and current workspace facts from the capability catalogue.
Git source control on BlinkHost
Choose what Git owns, what BlinkHost owns, and how browser drafts become intentional commits and verified releases.
Connect and import a GitHub repository
Authorize selected repositories, detect a frontend safely and import one exact commit into the browser workspace.
Repository manifest reference
Declare a portable frontend, module source candidates and logical resource names without storing privileges or secret values.
Git previews, protections and troubleshooting
Use pull-request previews without exposing production resources and recover safely from authorization, build or merge failures.
Install and maintain verified source templates
Start from a security-reviewed version and keep control of every future source update.
Edit project files together
Co-edit in the browser IDE, recover acknowledged changes after reconnecting and keep Git history intentional.
Git providers and enterprise controls
See which Git provider is available and configure access, policy reviews and downloadable evidence.
Manage or disconnect GitHub access
Understand repository access, disconnect a project and revoke an installation safely.
Hand a project over to a client workspace
Transfer a completed project only after the client authorizes its repository and accepts ownership.
Publish tested templates for teams and clients
Create an Agency publisher and release reusable source only after the exact commit passes a managed build.
Generate and download source evidence
Prepare a workspace-scoped record of source activity and download it before it expires.
Import an existing full-stack repository
Map a conventional frontend and compatible backend-module source without reorganising the repository around a BlinkHost starter.
Project portability and exit checklist
Know what source exports contain, what remains provider-managed and what to preserve before leaving.
Frontend and repository compatibility
Check a conventional repository layout, package manager and preview path before importing production source.
Data retention and connected-service boundaries
Understand what remains after disconnecting GitHub, what exports omit and how deletion requests are handled.
Build and operate projects with the BlinkHost CLI
Start safely, adopt existing repositories and operate BlinkHost from a terminal or automation workflow.
Developer release notes
Track CLI, SDK, runtime-contract, compatibility and migration changes.
How Git and source control work
Understand repository permissions, synchronisation, build identity and source ownership.
Data
Connect managed databases
Provision project data, use named bindings in preview and production, and keep provider credentials behind BlinkHost.
Native single-database transactions
Understand the native DEFAULT contract under production qualification: atomic batches, concurrency, operation receipts and regional reads.
Troubleshoot databases and named bindings
Resolve provisioning, schema, binding, query, and regional replica problems without exposing provider credentials.
Store files uploaded by your application
Upload, validate, deliver and manage application media without exposing storage credentials.
How hosted object storage works
Understand upload reservations, object isolation, integrity checks and delivery.
How managed databases and replicas work
Understand database bindings, transactions, replica freshness, isolation and recovery boundaries.
Domains Discovery
Connect a custom domain
Attach a customer-controlled hostname and verify DNS and certificate state before promoting it.
Add SEO and AEO metadata
Publish optional discovery metadata without making it a deployment prerequisite.
Troubleshoot custom domains, DNS, and certificates
Separate ownership, DNS propagation, routing, and TLS certificate readiness safely.
Secrets
Store and rotate application secrets
Keep credentials out of code with write-only, versioned and environment-scoped secret references.
Security assurance and account controls
Review available account protections, privileged access boundaries and procurement limitations.
Security assurance, data location and procurement
Distinguish published safeguards from independent assurance and contractual enterprise commitments.
How secrets and operational access work
Understand secret boundaries, runtime injection, rotation and support access.
Observability
Diagnose an application with logs and traces
Correlate bounded telemetry with the project, release, region, and W3C trace ID.
Diagnose a BlinkHost problem safely
Narrow a failure to the browser, project, release, region, dependency, or platform before changing state.
Troubleshoot telemetry and runtime policy changes
Interpret no-data states and recover safely from validation, publication, or propagation failures.
How application observability works
Understand tenant-scoped telemetry, retention, redaction and diagnostic evidence.
Runtime
Publish a versioned runtime policy
Validate, simulate, review, and roll back runtime changes without weakening platform security floors.
Control-plane API status and boundaries
Understand which routes support the dashboard and why browser credentials are not automation keys.
Browser control-plane contract v1
Review the deliberately limited, versioned contract used by BlinkHost's authenticated browser experience.
Preview a full-stack application with LiveStack
Connect a browser-local frontend to isolated backend modules and development resources before deployment.
How backend runtime isolation works
Understand capability-based functions, bounded execution and supported runtime surfaces.
Commercial
Understand plans, limits, and add-ons
Use the published commercial catalog to understand included capacity before making a platform decision.
Activate and manage a Microsoft Marketplace plan
Connect a verified Marketplace purchase to the intended BlinkHost workspace and understand where billing and product support are handled.
Track an agency or partner referral
Use an approved referral link, preserve attribution and understand when a benefit is reviewed.
Usage limits and what happens when you reach them
Understand monthly allowances, warning thresholds, hard limits, resets and add-on capacity.
Plans, capabilities and billing decisions
Compare current eligibility, add-on capacity, limit behaviour, payments and renewal outcomes before committing a workload.
Share feedback and control public use
Send product feedback, attach private evidence and control whether an approved excerpt may be used publicly.