Public projects & model cards
Publish an organization profile, share fine-tuned projects as public model cards, and let anyone try your adapters in the browser for free.
By default everything under arkor.ai/<org> is private — visitors without a session get a 404, and even the organization's existence is hidden. Publishing changes that per organization and per project: the same URLs serve members their private dashboard, and everyone else a public page. There is no separate "public site" to maintain — you publish the project you already have.
What visitors see
Two pages make up the public surface:
arkor.ai/<org>— the organization profile: the profile header (avatar, bio, company, location, links), join date, and the list of public projects. Private projects are simply absent.arkor.ai/<org>/<project>— the project's model card page: your Markdown description in the main column, an About panel (organization, base model, adapter type, run count, last update), a free demo chat, and a redacted list of training runs.
Everything else stays members-only: jobs, endpoints, the playground, usage, and settings all answer anonymous visitors with a 404. The run list on the card shows run name, status, base model, and dates only — dataset sources and URLs, hyperparameters, provider details, and artifact download links are never exposed.
Publishing an organization
In Settings, enable Public profile. Once enabled, arkor.ai/<org> becomes viewable by anyone and lists the organization's public projects.
Two things are permanent from that moment:
- Publishing cannot be undone. Once the profile has been public, its URL may already be indexed, linked, and cached — Arkor does not offer a switch that would only appear to undo the exposure.
- The organization's URL slug is frozen. The slug is the public URL itself; renaming it would put the indexed address back into the shared pool for someone else to claim. Pick the slug before publishing. The display name stays editable at any time.
Individual projects, however, can be switched back to private whenever you like — the profile stays up, the project disappears from it.
Anonymous trial organizations (created by the one-click App Server flow) cannot publish a profile.
Making a project public
Each project row in Settings has a Public page section with three controls. A project page is only reachable when both the organization profile and the project are public.
- Visibility —
Private(default) orPublic. Reversible at any time. - Model card — the Markdown description shown as the main column of the public page (details below).
- Showcase LoRA — optionally pin one completed training run. It is badged Featured on the public page and preselected in the demo chat. Only completed runs with a Final LoRA adapter qualify; with nothing pinned, the newest demoable run is the demo's default.
The View public page link next to Save shows exactly what a visitor sees — see Previewing.
Writing the model card
The card is standard Markdown with GFM extensions — headings, lists, tables, code blocks, block quotes, and links all render. A few rules keep owner-authored content safe to serve to anonymous visitors:
- Raw HTML is never executed.
<script>or any other tag is displayed as literal text. - Images must be
https://URLs on external hosts.http://images and images pointing back at Arkor's own domains are not rendered (the alt text shows instead). Hotlinked images are fetched by the visitor's browser, so host them somewhere reliable. - Links to external sites open in a new tab and carry
rel="nofollow". Relative links and links back into the app are rendered as plain text. - The card can hold up to 65,536 characters. Clearing the field removes the card; the page then shows the structured metadata only.
The free demo chat
Visitors can chat with your fine-tuned adapter directly on the card — no account required. The GPU time is funded by Arkor and is never metered against your organization's rate limits.
How it behaves:
- The demo serves Final LoRA adapters of completed runs only — checkpoints are never demoable. Visitors can switch between demoable runs; the showcase run is the default.
- Requests are clamped: up to 40 messages per conversation, up to 1,024 tokens per reply, and 64,000 characters of total conversation text.
- Traffic is rate-limited per visitor and per project (per-minute and per-day windows), so a popular card degrades gracefully instead of consuming unbounded resources. Visitors past the limit see a retry-later notice with a sign-up prompt.
- Demo conversations are not stored. Neither the prompts nor the completions are persisted anywhere.
- Demo requests currently appear in your project's Usage totals alongside your own traffic (they are recorded with a distinct internal source; a separate demo view is planned). Visitor identifiers in usage breakdowns are per-organization pseudonyms — different organizations cannot correlate the same visitor.
Previewing as a visitor
Append ?view=public to your organization or project URL — or use the View public page / View public profile links in Settings — to see the public page exactly as an anonymous visitor would, while staying logged in. Navigation inside the preview keeps the marker, and leaving it returns you to the dashboard. On a still-private project the preview shows the visitor's 404, which is itself informative: that is what the world currently sees.
Visibility and indexing
| Surface | Anonymous visitors get |
|---|---|
/<org>, /<org>/<project> (both published) | The public page, indexable by search engines |
| The same URLs, not (yet) published | 404 |
| An organization or project that does not exist | The same 404 |
| Jobs, endpoints, playground, usage, settings | 404 |
Private and nonexistent resources answer with an identical 404, so probing URLs reveals nothing about what exists. Public pages carry no noindex and are crawlable — treat everything on a published card as world-readable, including by search engines and archives.