Your development workspace.
Create web applications, run computations, collaborate and publish from a single workspace.
Create your first application.
Run a real API, choose a starter, edit your source and test it before you publish.
route GET "/api/hello" -> hello;
fn hello(req: Request): Response {
let name: String = query(req, "name", "world");
return json(200, {message: "Hello, " + name});
}Run the example to see its response.
Choose your workflow
From learning to deploymentEverything you can do with CLARA
Runtime status
Automatic startupQuickstart · from first API to deployment
1. Choose a starter in Projects. The editor automatically restores your draft on this device.
2. Compile in Build, inspect responses in Test, and run the project’s declared tests.
3. For hosting, create a private organization in Teams. In Deploy, enter its ID and administrator credential, compile and stage, then confirm promotion to preview or production.
Read the complete user guide · Hosting setup · Standalone installation diagnostics
Find the right software. Trust the source.
Search local, public and private developments. Connect verified registries with publisher-key pins, or discover a domain using DNS.
Search developments
0 matching releases
Trusted registries
DNS discovery sends your domain to Google Public DNS only when requested. A validated result pre-fills the connection; you approve the key separately.
Resolve a name
Select a verified release.
Choose a directory source to begin.
How trust, privacy and availability work
Signatures verify metadata integrity against a publisher key, not legal identity or endpoint safety. Public lookup uses live peer requests with no credentials. Private records never enter the public network. DNSSEC validation depends on the recursive resolver; CLARA does not independently validate the chain. Refresh peers for revocation changes; mirrors may omit or retain old records.
Your work, uninterrupted.
Build a queue, distribute verified work across browser tabs, and pick up where you left off.
Create a workload
Write a pure typed integer or Boolean function. GRID validates the full input range before saving the job.
Worker control
Enable this tab to process jobs. Open this same project in another tab and enable its worker to share the queue. Work stops when all enabled tabs close.
Opening persistent queue…
Job queue
Each completed shard is replayed and saved. Failed or expired leases can be recovered.
Keep the studio available
Optional public asset cache, checked against release SHA-256 hashes. Server routes, private data and analytics are never cached. Requires HTTPS and browser support.
Your projects
Choose a starter, edit, test, and export. Each project has isolated browser storage.
Source and tests are saved locally. Packages exclude database contents and credentials.
Archived projects
Archived drafts and their local data are retained on this device; restore to reopen.
Start something new
Ready-to-run templatesTests run automatically when opening a project, or run them again after editing. Tests compile the current draft and run in disposable storage. They never modify live data.
Edit test cases (JSON)
Application studio
Building a styled web application? Open the HTML / CSS / JavaScript application builder →
Recovery and full reset
Clear build removes compiled artifacts, not source or data. Reset starts a fresh draft and detaches its remote sync binding. No deployed release or database is deleted.
Recent build attempts
Compiler output
Initializing…
Route table
Try your application
Run a request.
Application data
Persistent notes
Versioned documents
Atomic compare-and-swap rejects stale revisions.
Runtimes & scheduling
WebAssembly compiler
Compile an active Int/Bool function directly to deterministic, import-free WASM. HTTP and storage stay in the capability VM.
Waiting for startup…
Server cron
Optional CLI jobs run without open browser tabs. Uploading alone does not install a cron entry. The sample job is read-only.
Configure cron using DEPLOY.txt. Token uses Requests tab.
IPFS release
The static release is available as a separate CAR archive. Gateway copies execute locally; they do not run CGI, cron or shared SQLite. No automatic publication or pinning.
Deployment and IPFS instructionsRun a function at scale.
One function, many inputs. Local worker lanes select compatible runtimes, then assemble reproducible results.
Detecting…
No server or account required. GPU compute is restricted to the reviewed integer kernel. Other pure Int/Bool functions run in WASM or VM. No source is shared across tabs.
01 / Define the work
Advanced distribution
Not sharing
Same origin and path only; helpers compute public integer ranges. All peer values are verified locally. No devices or remote servers are contacted.
02 / Run and verify
Ready. Start with the example.
Result and integrity receipt
No results yet.
The receipt commits to source, ordered outputs and shard boundaries. It is not a signature or proof of GPU identity. Replay verifies values. The demo is a correctness benchmark, not a speed claim.
Machine-readable Fabric specification →One function. Multiple targets.
Compile a pure numeric function, inspect the safety proof, then execute it on a compatible device. Your progress is saved on this browser.
Straight-line integer and Boolean expressions, immutable locals. For loops, recursion and web APIs use the existing Fabric or Build workspace.
Compile a function first.
Execution plan
No execution yet.
Backend selection is verified against the IR evaluator.
Verification & results
Every result is independently replayed before a backend-independent SHA-256 receipt is issued.
Complete an execution to generate a receipt.
Ready to compile.
Find software. Publish with confidence.
Give your applications, libraries and agents a stable CLARA name. Discover verified releases across local and hosted directories.
clara://namespace/app@1.0.0HTTPS · IPFS · MCPDevelopment directory
Local stays in this browser. Public and private server directories require the hosted CGI service. Private server access is administrator-only.
Search a directory to begin.
Create a release
Sign the current project's compiled package using a browser-held Ed25519 key. Local signatures do not publish your code.
Endpoints & dependencies (optional)
Keep this browser profile: signing keys are non-extractable and cannot be recovered after deletion. Public descriptions must contain no secrets. Metadata currently uses ASCII.
DNS bootstrap (optional)
For public records only. Add the descriptor to your own DNS zone if desired; this does not change normal DNS resolution.
Signature and machine-readable record
No automatic endpoint fetching or code installation. Verify the publisher key independently before trusting a release. Machine specification · NEXUS guide · Release schema
Connect CLARA to an agent
Model Context Protocol
Read-only public tools. Connect an MCP-compatible client over Streamable HTTP. No account or admin token needed.
Discover the server's tools to begin.
Client configuration example
Client configuration syntax varies. Protocol 2025-11-25, also 2025-06-18 and 2025-03-26. JSON response mode; no SSE or server sessions.
Public developer resources
Available tools
clara_manifest · clara_example · clara_routes · clara_fibonacci
Agents cannot access your editor draft, credentials, private analytics, storage or arbitrary server execution. Successful public tool calls contribute to aggregate usage counts.
Usage insights
Unlock analytics
Use the same server administrator token as the Requests console. Tokens and analytics reports stay in this page session.
No report loaded.
Daily active browsers
Daily counts table
Feature adoption
Agent tool usage
Metrics do not measure every visitor or unique person. They contain consenting browser identifiers, capped events and aggregate tool calls. Bots can inflate public counts. Reports use UTC and 90-day retention on service activity.
Your organization. Your software.
Collaborate through private, permissioned project vaults. Develop locally, explicitly save a revision, and share with invited teammates. Nothing is published to WORLD.
Open your workspace
Create an organization (hosting administrator)
Redeem an invitation
Keep credentials securely. They are not saved in browser storage. Administrators can issue replacements.
Connect or continue developing locally.
Your workspaces
Select organization
No project selected
Revision conflicts are rejected. Local copies are separate and are not automatically synchronized.
Members & invitations
Build together. Ship confidently.
Use verified libraries, keep projects in sync, share encrypted code, and deploy applications directly to your CLARA host.
Connect a private workspace
Use the organization ID and member credential issued in , or a limited API credential. Secrets stay in memory for this session.
Scoped API credentials
Create short-lived credentials for agents or other devices. A scope never grants permissions outside the parent membership.
Your projects, across devices
Push your current draft to this organization or pull a verified copy from another device. Revision checks prevent stale updates.
No selected project
Federated private discovery
Search up to eight trusted CLARA registries. Use a separate search-only scoped credential for each host. Remote hosts must explicitly allow this origin. Search queries and metadata pass to those hosts over HTTPS.
Compose with verified code
Resolve a published library by its CLARA name, or import a signed bundle. Pin publisher keys, then link exact versions into a new compiled project. Your original draft remains intact.
Registry installation retrieves signed public library records and their HTTPS JSON packages. Package hosts must permit cross-origin access.
Make a standalone library bundle
Export a signed library release in Publish, export its project package, and combine the files using CLARA-LIBRARIES-1. Libraries must be standalone compiled functions with no HTTP routes, templates or host storage calls. Exact dependencies are checked before source linking.
Share the package, not the secret
Encrypt locally with AES-256-GCM and PBKDF2-SHA256 (600,000 iterations). Only ciphertext is uploaded to encrypted object storage. Use a high-entropy passphrase and send it separately. This protects package content, not metadata or the downloaded frontend against a compromised host.
Encrypted workspace objects
New object
Test. Approve. Deploy.
Run the current project’s test suite, compile it, and publish an immutable server application under /Clara/apps/{release-id}/api/. Each release uses a separate database. Public GET routes are open; protected routes and writes require the hosting admin credential. Private GET routes also require organization membership.
No deployments in this session.
Administrator approval is required. Server receives reviewed bytecode, not anonymous source execution. Copy a deployed route to access it; previous active deployment URLs remain available until revoked.
Release manager
Compile, test and stage in one action. Review the server report, then explicitly promote to a stable URL.
Connect your organization
Members may inspect release history. Only the hosting administrator can register, check, promote or roll back releases.
Connect to begin. No credentials are saved.
Stage current project
Compile and run the current project's tests in local scratch storage. Register an immutable candidate without exposing its direct URL until promotion. Choose private for organization-only access.
Candidate releases each have independent storage.
Verify the candidate
Check report
No check in this session.
Tests execute uploaded bytecode in disposable storage with privileged test authorization. They do not prove source equivalence, production readiness or authorization behavior.
Promote or roll back
Rollback switches routing to a previously active, checked release. Data is not migrated or restored; each release retains its own database. Channel visibility cannot change.
Application credentials
Issue a release-specific API key instead of sharing the hosting administrator token. Select a release above. Keys expire and do not grant platform permissions. After promotion to a different release, issue new keys.
Release inventory
Promotion and rollback log
Machine-readable delivery protocol · MineSpace legal notices
Startup diagnostics
Deployment
Upload the contents of this folder to /Clara/. Browser execution and compatible hosted service initialization start automatically. Check runtime retries hosted initialization. The deployed server application is separate from the editor.
CGI requires executable permissions (755) on runtime.cgi and a Python 3 host. Server writes and private reads require a securely configured token. Read deployment instructions.
Local storage is specific to this browser and path. It is not shared with visitors or synchronized to the server.
Optional pseudonymous feature counts help improve CLARA. Analytics do not include code, credentials or request contents. Privacy notice.
Verify your installation
Check the uploaded asset inventory, server routes and protection of private files. No credentials are requested or transmitted. Use this after uploading or upgrading CLARA.
Ready to check.
Before publishing
Browser operation starts automatically. Hosted features require Python CGI and HTTPS. A working diagnostic probe is not a security audit.
- Preserve the hidden
.htaccessand executable CGI permissions. - Find the generated administrator token using your host's shell or private file manager, not through a public URL.
- Verify the server check, organization access, and a preview release on the actual hosting account.
- Configure HTTPS, public endpoint throttling, backups, and approve the legal notices.