JTF spec (Jootle Toolkit Format). The full schema for building custom toolkits. Published with the toolkit examples repo.
Adapter / connector reference. How to write integrations with external APIs as part of a toolkit.
API documentation. REST endpoints for working with your instance programmatically.
Webhook reference. Inbound and outbound webhook formats, HMAC signature verification, retry policy.

Links to the current versions of each are surfaced inside your instance under Settings → Developer. If a link is stale, ask your AI; it’ll point you at the live ones.

Architecture and security

Security architecture white paper. Detailed view of isolation, authentication, encryption, audit logging, and operational practices. Available to customers on request. Email security@jootle.com.
Ecosystem overview. A diagram-heavy explanation of how your instance, the control plane, and external services fit together. Useful for technical evaluators.

Compliance

SOC 2 Type 2 report. Available under NDA for customers on Business plans and above. Email security@jootle.com.
GDPR posture. Summary at jootle.com/privacy; full data processing agreement on request for EU customers.
HIPAA Business Associate Agreement (BAA). For customers on the Business plan with the HIPAA add-on. Email security@jootle.com.

Operational

Status page. status.jootle.com (or the link in your instance) for current platform health and incident history.
Maintenance window calendar. Available in Settings → Maintenance if you’d like to plan around upgrades.
Backup retention policy. The full text of the retention schedule and restore SLA, summarized in Backups and recovery.

Voice and writing references

For customers writing inside Jootle (or for content created by Jootle on your behalf):

Jootle voice guide. Style rules for the handbook (no em dashes, second person, Oxford commas, etc.). Source: STYLE.md in the jootle-knowledge repo.
Common patterns library. Templates for emails, briefs, weekly reviews, and other recurring artifact types. Available as a toolkit you can install from the library.

Community

Jootle community forum. jootle.com/community. For asking other customers, sharing toolkits, comparing notes.
Discord / Slack. Real-time chat with other customers and the team. Link in your instance settings.
Customer interviews. We run periodic interviews with customers about how they’re using Jootle, what’s working, and what isn’t. If you’d like to participate, email feedback@jootle.com.

Books and articles that influenced Jootle

A small recommended list for the curious. These are not authoritative, just things the team has found useful in the design of Jootle:

The PMBOK Guide (Project Management Institute), for the distinction between projects and programs.
Getting Things Done, David Allen, for the inbox-style capture pattern and the trust-the-system principle.
Designing Data-Intensive Applications, Martin Kleppmann, for the operational philosophy behind the database and knowledge graph.
The Power of Habit, Charles Duhigg, for the rhythm of goal-driven habits Jootle helps support.

These aren’t required reading. But if you want to understand why Jootle’s design decisions land where they do, they’re a starting point.

External tools that pair well

A few tools that play well alongside Jootle, without being part of it:

Obsidian or any plain-Markdown notetaking app. For the writing you’d rather do offline. Jootle can read and write Markdown easily.
Stripe. For payments. Jootle’s billing uses Stripe; if your business does too, the integration is smooth.
Google Workspace. Already covered in detail. Best-supported email and calendar.
Linode / DigitalOcean / similar. If you’re operating multiple Jootle instances yourself in an unusual setup, basic familiarity with cloud providers helps. Most customers never need this.

When in doubt

Email support@jootle.com. We’re happy to point you at the right resource if this page doesn’t.

Further reading

Developer references