Local-first desktop software
Desktop-first applications for cases where local storage, runtime boundaries, and operator control should be explicit from the start.
Capabilities
Software work at Tenra.
Tenra.dev is the software development division of JAMARQ Digital LLC. JAMARQ handles client-facing web systems and digital infrastructure; Tenra focuses on products, internal tools, software systems, and a limited number of aligned custom engagements.
Current software efforts are listed on the projects page.
Internal tools and operational systems
Systems for tracking organizations, customers, assets, assignments, workflows, and the parts of operations that need a stable source of truth.
AI mediation and control layers
Software that constrains model behavior, preserves provenance, rewrites output under clear rules, or keeps humans in the approval loop.
Research-oriented software systems
Experimental or exploratory builds used to test a reasoning model, interface pattern, or systems approach without pretending the work is finished.
Selective custom software work
A secondary path for a limited number of outside projects when the work is aligned, technically specific, and suited to Tenra's software environment.
How Tenra approaches the work
- Products and internal systems lead the work here.
- Local-first and desktop-first approaches are used when they improve control or correctness.
- Generated output should remain inspectable and, where needed, human-approved.
- If a project is early or experimental, it stays labeled that way.
Where custom software work fits
Tenra is primarily a home for JAMARQ's own software. Outside work is still possible, but it is selected carefully and kept secondary to product and internal systems development.
Good fit
- Internal tools with clear operators and workflows
- Operational systems that need a reliable system of record
- AI mediation layers with explicit constraints
- Local-first applications where data ownership matters
- Domain-specific software with narrow, knowable scope
Selection
Projects are chosen for fit. The bar is whether the work belongs in a calm, technical software environment with clear boundaries.
Need to ask about a fit?
Send a concise description of the system, the operators, and the constraints. If the project belongs here, we'll continue the conversation. If it does not, we'll say so plainly.