Independent application infrastructure, tools, and applications for ChatGPT Sites.
AittaDB develops source-available software for persistent, authenticated applications running on OpenAI-hosted ChatGPT Sites.
At its center is the AittaDB server: a reusable application backend providing identity, data, files, and events through one self-contained deployment. The organization also develops applications and tools that use these primitives or explore independently controlled software built on the same platform.
AittaDB is experimental, under active development, and independent of OpenAI. It is not an official OpenAI project.
| Project | Role |
|---|---|
| AittaDB | The core application backend. It provides identity, OAuth 2.0 and OpenID Connect sessions, persistent JSON data, object storage, HTTP APIs, and feature-gated immutable typed events with bounded reads and long-polling delivery. |
| AittaSocial | Independently controlled social software. One deployment runs one Aitta: an application with its own identity, content, appearance, configuration, canonical address, and D1 data. The current proof of concept supports public identity and publishing without requiring the Hub. |
| AittaSocial Hub | The central service and project website for the developing Aitta Network. Its planned responsibilities include trusted Hub identity, owner-authorized connections, discovery, relationship metadata, scoped access, and network enforcement. AittaDB provides its central state layer, but the Hub does not own content held by independently controlled Aittas. |
aitta CLI | The early-stage command-line client for authenticating with AittaDB and working with applications, sessions, records, files, and persistent events. |
| Investor App | An experimental, configurable application for publishing private investor information and collecting non-binding founder applications and investment-interest indications. It is being developed to use AittaDB as its production state layer. |
These boundaries are deliberate. AittaDB provides small, reusable backend primitives, while each application owns its product-specific behavior and policies.
An AittaSocial Aitta stores its content in its own deployment-owned D1 database; it does not need a separate AittaDB instance or shared Hub content store. The Hub can use AittaDB for its limited central state without moving ownership of independently controlled content into the Hub.
An Aitta is an independently controlled AittaSocial application. It may represent a person, company, project, community, publication, AI agent, or another kind of entity.
An Aitta owns its local identity, content, configuration, data, behavior, and access policy. It may be publicly readable, participate privately through authorized Hub connections, or operate without the Hub. A private Aitta may access authorized network views without itself becoming publicly available on the internet.
The planned Aitta Network is based on typed events and parent-linked threads:
- Every event has a globally unique identifier and a namespaced type.
- An event may reference zero or one other event as its parent.
- A parentless event originates a thread.
- A child event extends the thread while retaining its own type and meaning.
- A thread may contain events created by several independently controlled Aittas.
- Each Aitta remains authoritative for the events it creates, not for the entire distributed thread.
- A feed is an ordered, filtered, and access-controlled projection of events—not a content owner or storage boundary.
For example, an article may originate a thread. A social.aitta.comment event can reference that article as its parent, another comment can reference the first comment, and a reaction can reference any of those events without becoming a comment itself.
AittaSocial reserves event types under the reverse-domain namespace social.aitta.*, derived from aitta.social. Other domain owners can define compatible event types under their own reverse-domain namespaces.
An event type describes semantics; it does not by itself establish authenticity, authorization, trust, or domain ownership. Those remain protocol and security responsibilities.
The parent-linked Aitta Network model is planned architecture. The current AittaSocial proof of concept still uses its existing versioned entry resources and does not yet implement distributed threads, comments, reactions, private network feeds, or complete Hub connectivity.
The current AittaDB development preview includes:
- ChatGPT-based upstream identity mapped to an independent AittaDB identity
- OAuth 2.0 and OpenID Connect sessions for connected applications
- Persistent structured JSON data
- Object and file storage
- Immutable typed event publication, bounded reads, and cursor-based long polling behind a default-off feature flag
- Human-facing HTML interfaces and versioned hypermedia JSON representations
- HTTP APIs for websites, services, command-line tools, native applications, and AI agents
Additional access-control primitives, network-specific event relationships, and other capabilities remain under development.
AittaDB deliberately provides general-purpose primitives rather than embedding social-network, investor-management, payment, membership, or other product-specific workflows into the database server.
AittaDB is designed to run as a self-contained deployment on ChatGPT Sites. Its current implementation uses platform-provided capabilities including:
- Managed application hosting and runtime
- Sign in with ChatGPT
- D1 relational storage for durable structured data
- R2 object storage for files and binary data
- Hosted environment configuration and secrets
Because these capabilities are supplied by ChatGPT Sites, a core AittaDB deployment does not require a separate application server, database server, object-storage service, or authentication service.
Each deployment remains independently configured and owns its issuer, signing keys, database, object storage, users, and application data.
ChatGPT Sites is currently in public beta. Availability, supported capabilities, and resource limits may depend on the account, plan, region, and workspace configuration and may change during the beta.
In Finnish, an aitta is a traditional detached storehouse on a farmstead. It was built to keep grain, food, tools, and other valuable supplies safe and available.
AittaDB follows the same idea for application infrastructure: a dependable place for identity, data, files, and events.
Within AittaSocial, an Aitta carries that idea further. It is an independently controlled application that keeps its own content and identity while choosing how—and whether—to participate in the wider network.
The projects are under active development. Their interfaces, protocols, terminology, and operational requirements may change before stable releases.
Current AittaDB, AittaSocial, and Investor App releases use the source-available FSL-1.1-MIT license. Each released version converts to the MIT License two years after its publication. Consult each repository’s license for its exact terms.
You can contribute by:
- Deploying and testing AittaDB or AittaSocial on ChatGPT Sites
- Building applications that use AittaDB
- Experimenting with independently controlled Aittas
- Reporting bugs and compatibility problems
- Proposing real-world use cases and event types
- Developing client libraries, command-line tools, and integrations
- Improving documentation and protocols
- Reviewing security, privacy, and ownership boundaries
- Submitting focused pull requests
- Supporting the projects as an early startup investor
Please read the contribution and agent instructions in each repository before making changes.
AittaDB is currently in its pre-startup stage. In addition to technical contributions, I am open to conversations with people interested in supporting AittaDB, AittaSocial, and the developing Aitta Network as early startup investors.
This is currently a friends-and-family-style phase—although I am very open to making new friends who believe in the idea.
This is an invitation to start a conversation, not an announcement of a formal funding round or securities offer. If you are interested, contact me through my GitHub profile or my LinkedIn profile.
- Visit the live AittaDB development service
- Explore AittaSocial and the Aitta Network
- Browse the AittaDB organization
- Use GitHub Issues for bug reports and focused proposals
- Read the ChatGPT Sites documentation
- Visit the founder’s GitHub profile: @thejhh