Thanks to visit codestin.com
Credit goes to kernaio.com

Skip to content
Features

6 modules in the product, 7 on the roadmap.

Each of these is a module: it owns its data, its API and its screens, and a workspace can switch it off. What they share is the part that usually costs you an integration — the people, the permissions, the search, the history and the inbox.

Every module below says whether it is available now, being built, or on the roadmap — and the list under each one separates what it does today from what it does not do yet. Kern is pre-1.0 and we would rather you knew exactly what you are getting.

Issues & projects

Available now

A tracker that holds up to a real engineering process, and still opens in a keystroke.

  • Work item types with hierarchy — initiative, epic, story, task, sub-task — and your own types beside them
  • Custom fields: text, number, date, select, user, label, URL, checkbox and relation, placed per work item type
  • Workflows with statuses, transitions, conditions, validators and approvals
  • List and board views, grouped by status or by any custom field
  • KQL — a query language over every field, saved and shared as views
  • Cycles, milestones, versions, components, labels and backlog ranking
  • Relations, sub-issues, watchers, threaded comments with mentions, reactions and attachments
  • A triage queue that accepts, declines or snoozes what comes in
  • Time tracking: timers, worklogs, and estimates against what was logged
  • Reports: burndown, velocity, created-versus-resolved, and time
  • A public intake form a stranger can fill in, repeating issues, and import
  • A visual editor for workflows
  • Keyboard-first throughout, with bulk edit

Still to come

  • Calendar and timeline views
  • Post-functions that run when a transition does
  • Email that becomes an issue
  • Links to GitHub and GitLab
kern · Issues & projects

Chat

Available now

Team chat that knows what an issue is — because it is the same application.

  • Public and private channels, direct messages and group DMs
  • Object channels: a conversation that belongs to one issue, opened from the issue itself
  • Threads, reactions, mentions of a person, a group or a channel
  • Read state and unread counts per channel, not per message
  • Pins, bookmarks, saved items and full-text search
  • File sharing with previews for images, audio and video, and code blocks
  • Voice and video messages
  • Presence, typing indicators, status, mute and do-not-disturb
  • Slash commands in the composer: /me, /shrug, /topic, /leave, /mute and /unmute

Still to come

  • Turning a message into an issue, with the thread attached
  • Huddles — they wait on the calls module
  • Slash commands of your own, beyond the six built in
  • Incoming webhooks: a channel can already receive one, but nothing issues a token yet
  • Unfurling a link that is pasted into a message
kern · Chat

Docs

Available now

A wiki with your issues, files and people in it, edited by everyone at once.

  • Spaces, with pages nested as deep as you need
  • Access checked per space and per page, by the same permission model as everything else
  • The editor: several people typing at once, many cursors, no save button
  • Comments and mentions
  • Version history
  • A published version and a draft, so a documentation site never shows half-written text; a published site addressed by path
  • Databases inside a page, diagrams, and embeds that unfurl
  • Every page in global search

Still to come

  • Export as Markdown or PDF
  • Whiteboards
kern · Docs

Mail

Available now

Email that leaves Kern reliably, with one log of what was sent and what bounced.

  • Outbound sending per workspace: SMTP, Mailgun, SES, Postmark or Resend
  • Templates, a send queue, and a delivery log you can actually read
  • Bounce handling and a suppression list, so a dead address stops being retried
  • A test send from the settings page, so the configuration is proven before anything depends on it

Still to come

  • Intake addresses that file mail straight into a project as an issue
  • Your own IMAP account inside Kern — folders, search, compose, reply
  • Signing in to a mailbox with Google or Microsoft
  • Linking an email to a contact or a candidate, once those modules exist
kern · Mail

Drive

On the roadmap

Object storage with the manners of a file manager. Files already attach to issues and messages; Drive is the module that gives them a home of their own.

What it will do

  • Folders and files with resumable uploads that survive a dropped connection
  • Versions on every file, with restore
  • Share links with an expiry date and an optional password
  • Previews for images, video, PDFs and office documents
  • Trash and restore, with per-workspace quotas
  • One copy of a file, attached in many places
kern · Drive · planned

Calendar

On the roadmap

Meetings, sprints, interviews and time off on the same grid.

What it will do

  • Personal and shared team calendars
  • Events, all-day events and recurrence
  • Reminders, and a call link on any event
  • Overlays for cycles, leave and interviews from the other modules
  • Availability when you schedule with colleagues
  • ICS export for anything else you use
kern · Calendar · planned

HR

Available now

HR that shares one directory with the rest of the company’s work, on the same approval engine as the tracker.

  • A directory of people: employment details, manager, department, position and office
  • Org chart and offices
  • Leave types and balances, routed through the same approval engine as everything else
  • Attendance, shift rosters, and an approvals inbox
  • Holiday calendars with country packs, legal entities and cost centres, payroll export
  • Onboarding and offboarding checklists that create real tasks
  • Subject access and erasure for the person the record is about

Still to come

  • Performance reviews
  • A calendar overlay of who is away, once Calendar exists
kern · HR

Inventory

Available now

An asset register that answers the question a laptop raises — whose is it, and since when — in one row.

  • Assets with a server-assigned tag, serial number, purchase, price, warranty, location, photo and category
  • Custody: hand an item over, on, or back, with the whole chain kept and the receiver told
  • A return list when somebody leaves — nothing is moved on their behalf
  • Categories you order by dragging, and custom fields per category
  • Repairs and the files that go with them; a warranty or a repair that has run long raises a notice
  • A history read as sentences, and a tag that resolves from the command palette

Still to come

  • Reservations
  • Bulk import from a spreadsheet
kern · Inventory

Recruiting

On the roadmap

An applicant tracker that would hand a hire straight to HR.

What it will do

  • Vacancies and a talent pool that outlives a single opening
  • Applications moving through pipeline stages on a board
  • Interviews scheduled on the calendar and scored on a scorecard
  • Offers, and a hire that becomes an employee record without re-typing
  • A public career page and an apply form on your own domain
  • Email a candidate from inside their record
kern · Recruiting · planned

CRM

On the roadmap

A sales pipeline in the same application as the team that ships the thing.

What it will do

  • Contacts, companies, leads and deals
  • Several pipelines, each a board with its own stages
  • Activities, notes and tasks against any record
  • Emails linked to the contact automatically
  • Custom fields, the same engine the tracker uses
  • A web-to-lead form, and CSV import
  • Pipeline and forecast reports
kern · CRM · planned

Automation

On the roadmap

One rule engine, with every module registering its own triggers and actions into it.

What it will do

  • Triggers: created, updated, transitioned, commented, scheduled, manual, webhook, email received
  • Conditions on any field, any KQL query, any user or group
  • Actions from every module: edit, transition, assign, comment, create, message, email
  • Branches that act on sub-items, related items or a query
  • Smart values — {{issue.key}}, {{user.name}} — anywhere a string is accepted
  • Scoped to a workspace or a single project
  • A run log with the reason a rule did or did not fire, and a retry button
kern · Automation · planned

Calls

On the roadmap

Calls on LiveKit, started from wherever the conversation already is. The self-hosted stack can already bring a LiveKit server up; the module that would use it is not written.

What it will do

  • One-to-one and group audio and video
  • Starting a call from a channel or a calendar event
  • Screen sharing
  • A huddle: the low-ceremony call that lives inside a channel
  • A self-hosted media server, so the audio does not leave your infrastructure
kern · Calls · planned

AI assistant

On the roadmap

Useful AI with an honest boundary: nothing would leave your instance unless you configured it to. Nothing is sent anywhere today, because there is nothing to send it.

What it will do

  • Bring your own key — Anthropic, OpenAI, any OpenAI-compatible endpoint, or Ollama on your own hardware
  • Summarise a thread, an issue, a document or an email
  • Draft an issue, a reply or a document section
  • Semantic search across everything you are allowed to see
  • Ask @kern in any channel
  • Off by default, per workspace, with the key held encrypted
kern · AI assistant · planned
The platform

What every module gets for free.

None of this is per-module work. A module declares what it needs and the platform provides the rest.

Many workspaces, one inbox

Belong to a company, a client and a side project at once. Notifications from all of them arrive in a single inbox with a badge per workspace, over one connection.

Permissions that go down to the object

Modules declare permission keys. Roles are sets of keys, bound at workspace, project or object level. Guests see exactly the projects you named and nothing else.

One search across everything

Command-K reaches issues, messages, documents, files and people — and only ever returns what you are allowed to see.

English, German, Persian, Arabic, Turkish

Every string is translated, and the interface is built with logical properties, so right-to-left is a real layout rather than a mirrored afterthought.

Notifications you can actually tune

Per event type, per channel: in-app, push or email. Mentions, assignments and watches follow their own rules. Web push works on the phone, including iOS.

A public API, not an afterthought

Every screen is built on the same REST API you get, described by OpenAPI 3.1, with scoped API keys you issue and revoke yourself. Outgoing webhooks are on the roadmap.

An activity log under everything

Each object carries an append-only history. It powers the timeline you read, the feeds you follow and the audit log an auditor asks for.

Modules own their data

Each module holds its own Postgres schema, with row-level security on its tenant tables — most of them today, and the migrations name the rest. One module cannot read another’s tables — it has to ask through a contract.

Installs like an app

A progressive web app: install it from the browser, keep it in the dock, get badge counts and push, and read recent work when the train goes into a tunnel.

Yours to audit

Every line that touches your data is public. Sessions, passkeys, roles and permission bindings, encrypted per-workspace secrets — all of it readable before you trust it. Sign-in with Google, GitHub or Microsoft, and single sign-on over OIDC or SAML, are on the roadmap.

Everywhere you work

Five languages, both directions, light and dark.

Persian and Arabic are not a mirrored stylesheet. The interface is laid out with logical properties from the start, so a right-to-left workspace is the same product, not a degraded one.

  • English, German, Persian, Arabic and Turkish, switchable per person
  • Right-to-left layout, including boards, panels and shortcuts
  • Light, dark, or whatever the operating system says
  • Installs as an app on desktop and phone, with badges and push
  • Keyboard-first: everything reachable without the mouse
kern · فارسی
kern · mobile

See it with your own work in it

Start a workspace on the cloud, or put it on your own machine this afternoon.

curl -fsSL https://get.kernaio.com | bash