Local-first product boundaries
Testing how desktop-first tools should store data, expose handoffs, and stay useful without turning everything into a cloud account.
Tenra
Local-first software, internal tools, AI control layers, and durable systems with clear boundaries.
Tenra is the software development division of JAMARQ Digital LLC, built around tools and prototypes whose reasoning stays visible.
Creator operations
Creator Suite
Vaexcore Studio by TenraVaexcore Pulse by TenraVaexcore Console by TenraVaexcore Relay by Tenra
Business operations
Business Suite
Atlas by TenraMarketDesk by TenraSiteOps Core by TenraStageDesk by Tenra
Research + control
Research Suite
Scout by TenraFacet by TenraDerive by TenraSentinel by Tenra
Records + readiness
Finance/Records Suite
Ledger by TenraRegistry by TenraAlign by Tenra
Community + utilities
Community/Utility Suite
Vicina by TenraRegional Game Clock by TenraCrossCurrent by TenraPartition by Tenra
A named place for artifacts, not vapor.
The work here should leave behind tools, notes, experiments, and implementation choices that can be inspected later.
Local-first when custody matters
Readable state over hidden magic
Human approval where automation can drift
Artifacts that leave reasoning behind
Tools and systems in motion.
Tenra work is organized around clear product surfaces: command centers, guardrails, reasoning layers, and specialized planning tools.
Tenra Hub
Command Center planning for the suite: catalog, readiness, integration interfaces, status, links, and next actions.
Guardrail
A local-first control layer for what AI agents are allowed to touch, call, or change.
Derive
A structured answer system that keeps assumptions, evidence, confidence, and context visible.
Partition
A safe partition-planning surface for simulations, refusal checks, and non-destructive exports.
Notes make the work reusable.
Public notes keep the reasoning visible: infrastructure choices, interruption-safe workflows, and what prototypes proved.
Read all notesThe Value of Boring Infrastructure
Why Tenra favors clear local data, readable workflows, and boring operational foundations before clever interfaces.
Designing Small Systems That Survive Interruption
How Tenra thinks about resumable workflows, visible state, and tools that survive real-world interruptions.
Why Prototypes Should Leave Notes Behind
A Tenra note on preserving the reasoning behind experiments so future product decisions are easier to make.
AI control surfaces
Exploring where automation should stop, what humans should approve, and how output can remain inspectable.
Artifact-backed product notes
Keeping public notes near the work so prototypes do not lose the reasoning that made them useful.