Перейти к содержанию

Product Overview

What is SmartKitten?

SmartKitten is a B2B platform for organizations that want to combine AI-assisted work, secure document storage, reMarkable tablet workflows, and field edge sync (stations) in a single product.

Each customer operates inside an organisation (tenant). Users authenticate once, consume services according to their subscription plan, and interact through a unified web application.

Target customers

Segment Typical need
Knowledge-intensive teams AI chat, document tools, note capture from tablets
Distributed / field operations Stations on site, tablet sync without manual file juggling
Regulated or private deployments Self-hosted infrastructure, org-scoped data

Value proposition

  1. One workspace — chat, files, boards, and tablet artifacts in one UI.
  2. AI with context — MCP tools let agents read/write documents and fetch the latest tablet screenshot.
  3. Tablet-native pipeline — reMarkable .rm files, conversion, screenshots, bidirectional sync via stations.
  4. Commercial control — plans, entitlements, token quotas, and usage accounting.
  5. Microservice architecture — domains (account, billing, device, …) evolve independently behind a single API gateway.

Core capabilities

Capability User-visible outcome
Identity & orgs Register, join org by tagline, roles, supervisor hierarchy
AI chat OpenAI / Gemini sessions, OCR, image generation, tablet commands
Documents & MCP Folders, versions, agent tools (documents.*, screenshot tool)
Devices & stations Register stations, assign tablets to users, telemetry, screenshots
reMarkable Upload notes, sync commands, extract / insert / restore
Boards Projects, sticky notes, collaborative editing sessions
Billing Plans (free → enterprise), subscriptions, quota enforcement

Architecture (high level)

flowchart LR
  User[User_Browser] --> FE[Frontend]
  FE --> GW[Nginx_Gateway]
  GW --> Services[Microservices]
  Services --> DB[(PostgreSQL)]
  Station[Station_Agent] --> GW
  Tablet[reMarkable] --> GW

Out of scope for this document

Technical API details, deployment runbooks, and infrastructure secrets are covered in Technical Reference and individual service repositories.