Thousand

Product Introduction

1. Definition: Thousand is a documentation engineering platform. It is a Git-backed documentation system that functions as a managed, access-controlled remote for a Markdown repository. It sits in the technical categories of knowledge management, developer tooling, and collaborative documentation.
2. Core Value Proposition: Thousand exists to solve the fundamental conflict between open collaboration and secure information sharing in modern, AI-integrated teams. It provides a single source of truth in plain Markdown while enforcing granular, folder-level access control for humans and AI agents, eliminating document drift and permission sprawl.

Main Features

1. Git-Backed Single Source of Truth: Every document is a file in a Git repository. There is no separate database or proprietary format; the canonical document is the Markdown file. How it works: The platform acts as a smart Git remote (git.usethousand.com). When users edit via the web interface, each save generates a named Git commit (e.g., a3f19c2), preserving full history. This ensures documentation is always synchronized with engineering workflows.
2. Granular, Path-Level Access Control: Unlike standard Git (all-or-nothing access), Thousand implements access control lists (ACLs) at the folder level. How it works: Administrators define rules (e.g., design/** -> leo:write, notes/** -> summarizer-bot:read). These rules are enforced at the platform level, filtering the repository view and Git fetch/pull operations for each user or agent, even if they never use a Git client directly.
3. Integrated AI Agent Management: AI agents are treated as first-class members of the workspace, not add-ons. How it works: Each agent gets a named profile, a dedicated API token with a mandatory expiry date, and explicitly defined read/write permissions to specific folders. This provides auditability and security, treating agent access with the same rigor as human user access.
4. Multi-Format Document Hub: The platform natively renders and manages non-Markdown files within the same access-controlled repository. How it works: Office files (.pptx), PDFs, images, Excalidraw diagrams (.excalidraw), and CSVs are stored as binary or text files in Git. They are rendered in the web UI, made searchable by their textual content (OCR for PDFs), and are editable (where applicable) under the same permission rules.
5. Context Sync from Codebases: Automatically mirrors documentation from external code repositories. How it works: Thousand can be configured to watch specific folders (e.g., /docs, /context) in connected GitHub or GitLab repos. On every commit, it syncs the content into the workspace as a read-only, source-stamped directory, ensuring codebase documentation is always current without manual copying.

Problems Solved

1. Pain Point: Documentation Silos and Drift. Teams struggle with multiple, unsynchronized copies of documentation across Notion, Google Docs, Confluence, and README files in codebases, leading to outdated and conflicting information.
2. Pain Point: Insecure or Overly Broad Knowledge Sharing. Sharing a Git repo gives collaborators access to everything. Sharing a link to a cloud doc often requires account creation or provides no fine-grained control, creating security and compliance risks.
3. Target Audience: Engineering & Developer Relations Teams who need to maintain accurate, version-controlled documentation that is tightly coupled with code. Founders and Technical Leaders who need to share sensitive information (finances, strategy) with specific board members or advisors without using insecure channels. Product & Design Teams who collaborate on specs and research but need to integrate those documents with engineering deliverables.
4. Use Cases: Onboarding External Contractors with access only to the /onboarding and /project-spec folders. Providing Context to AI Coding Assistants like GitHub Copilot or Cursor by giving them secure, read-only access to the /eng/api-server docs. Creating a Board Portal where sensitive /finance/ and /strategy/ documents are accessible via a simple, revocable link for non-technical members.

Unique Advantages

1. Differentiation vs. Traditional Wikis (Notion, Confluence): Thousand's documentation is portable, version-controlled Markdown files, not locked in a proprietary database. Exit is a simple git clone. Unlike these tools, it offers true file-level permissions and seamless integration with AI agents as core members.
2. Differentiation vs. Raw Git (GitHub/GitLab Wikis): Thousand adds a user-friendly, non-technical interface for editing and browsing, sophisticated access control that Git lacks, and native handling of binary files and comments stored alongside files (not in commit messages or forks).
3. Key Innovation: The core innovation is the "permission-shaped workspace." It presents a unique, filtered view of a single Git repository to every user and AI agent based on their ACLs. This merges the universality of a mono-repo with the security of micro-repos, all while maintaining a single commit history.

Frequently Asked Questions (FAQ)

1. How does Thousand handle access control for users who don't have a Git account? Thousand provides shareable links for any document. Recipients can view the content in their browser with no sign-up required. The link can be set to "anyone with the link" or specific emails, and can be revoked instantly by the workspace owner.
2. Can I use Thousand with my existing GitHub or GitLab repository? Yes. You add Thousand as a new Git remote (git remote add thousand ...) and push your existing history. It works alongside your existing origin remote (e.g., GitHub) without conflict, acting as a filtered, managed view.
3. What happens to comments and annotations? Are they saved in the Markdown files? No. Comments and threads are stored beside the document, not inside it. They are saved as structured data (in Markdown format) that a git clone will include, ensuring the conversation history is preserved and portable without polluting the source document files.
4. Is Thousand suitable for non-technical team members like marketers or executives? Absolutely. The platform provides a clean, intuitive document editor (like Google Docs) for editing Markdown without seeing the syntax. For pure consumers, documents are simply web pages or shareable links, requiring zero technical knowledge of Git or Markdown.
5. What is the exit strategy? Is there vendor lock-in? There is no lock-in. All content, including file history, is stored in your standard Git repository. You can stop using the Thousand service at any time and run git clone to retrieve your complete documentation repository with full commit history, in open Markdown and associated file formats.