Your team already solves hard problems. Make sure it never solves them twice.
Turn internal patterns, recurring errors, reviewed fixes, and private documentation into a trusted technical memory—available beside every browser tab and hosted inside infrastructure you control.
From “ask Sarah” to an answer the whole team can trust.
DevRecall Team adds a small internal service to the extension your team already uses. The service owns the database, identity, permissions, review state, and audit history.
Deploy one small service
Run the provided Docker Compose package on a laptop, VM, or internal server. Tables are checked and created automatically.
Register the workspace
The first owner enters the internal URL and Team license. The server validates the Team variant with Lemon Squeezy and creates the workspace.
Invite the right people
Share the service URL and rotating invite code through an approved channel. New members enter as Viewers until an owner assigns a role.
Build trusted memory
Editors contribute patterns, errors, fixes, and documentation. Admins review and verify the answers everyone should rely on.
Capture the answer—and why your team chose it.
Shared patterns
Put approved SQL, JavaScript, Snowflake, Excel, Regex, Git, PowerShell, and internal conventions into the same intent-based search.
Internal error memory
Record the symptom, root cause, safe correction, and verification steps behind errors that public search cannot understand.
Verified fixes
Separate an individual draft from a reviewed team answer. Editing a verified entry returns it to review so trust is never implied.
Private documentation
Keep concise runbooks, release checklists, operational notes, and implementation decisions close to the work instead of lost in another portal.
Portable workspace
Export workspace knowledge as readable JSON for controlled transfer, archival, or review—without giving browsers access to the live database.
Activity trail
See registrations, contributions, submissions, verification, role changes, invite rotation, and deletions in a workspace-level history.
Give every person exactly the access they need.
Permissions are checked by the Team service for every mutation. Hiding a button is useful UX; rejecting unauthorized API requests is the real control.
Explore the security model →Search and use available team knowledge.
Create drafts, update entries, and submit work for review.
Verify fixes, moderate knowledge, and manage operational content.
Control membership, roles, invitations, and workspace access.
Your knowledge stays behind the boundary you choose.
The Chrome extension talks only to the internal service URL approved by the user. The service—not the browser—opens SQLite and enforces workspace rules.
Local database ownership
SQLite lives on storage attached to the service host, never in a browser or shared network folder.
Controlled registration
Team licenses are checked against configured Lemon Squeezy store and variant IDs. Existing workspaces require an invite code.
Protected credentials
Session tokens and invite codes are stored as hashes server-side. License keys are not stored in the extension.
Deliberate network access
Chrome requests permission only for the supplied service origin. Production deployments use trusted HTTPS and an explicit CORS allowlist.
Deploy where your team already operates.
Start on a Windows laptop with Docker Desktop, or place the same service behind HTTPS on your internal Linux or Windows server.
- API service
- Available
- Database
- Connected
- Workspace data
- Your infrastructure
- Support
- Built by Kris
Every solved problem becomes a faster next answer.
Recurring internal errors return the fix and context your environment actually needs.
Verification signals distinguish a useful draft from a team-approved answer.
New colleagues discover working conventions in the same place they search for syntax.
Critical implementation context stops living only in messages, meetings, and memory.
What your technical and security teams will ask.
Is DevRecall Team a hosted SaaS knowledge database?
No. You deploy the Team service and own its SQLite database. Built by Kris does not host your workspace content in this edition.
Does every browser connect directly to SQLite?
No. Only the internal service opens the database. Extensions communicate with its authenticated HTTPS API.
How do invitations work?
The first licensed registration creates an owner and one-time invite code. New members use the service URL, Team license, and current invite code. Owners can rotate that code at any time.
Can we control who publishes trusted answers?
Yes. Editors create and submit knowledge; admins and owners can verify it. A verified entry returns to draft if its content changes.
Can we back up or move a workspace?
Yes. Use database backups for full recovery and JSON exports for portable workspace knowledge. The deployment guide covers both.
Can it start on one machine?
Yes. A Team evaluation can run through Docker Desktop on a Windows laptop. Wider access should use a trusted HTTPS hostname on an internal server.
Tell us how your organization works. We’ll help shape the right Team deployment.
Share your approximate team size, preferred server environment, and security requirements. We’ll respond with a practical deployment and licensing path.
No obligation. Direct contact with support@builtbykris.com.