Local-first desktop software
Desktop-first and local-first applications for cases where storage, runtime boundaries, data custody, and operator control should be explicit from the start.
Capabilities
Custom software work at Tenra.
Tenra focuses on software products, internal tools, local-first systems, AI control layers, and a limited number of aligned custom engagements. The work belongs here when it needs operators, state, data boundaries, approvals, or runtime behavior that stays legible.
Current software efforts are listed on the projects page.
Internal tools and operational systems
Custom internal tools for tracking organizations, customers, assets, assignments, documents, workflows, and the parts of operations that need a stable source of truth.
AI mediation and control layers
AI control software that constrains model behavior, preserves provenance, rewrites output under clear rules, or keeps humans in the approval loop.
Research-oriented software systems
Reasoning, market research, signal aggregation, and decision-support systems that expose context, assumptions, evidence, and confidence.
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 product and internal-systems surface. Outside work is still possible, but it is selected carefully and kept secondary to product development.
Good fit
- Internal tools with clear operators and workflows
- Operational systems that need a reliable source of truth
- AI mediation layers with explicit constraints and approval points
- Local-first applications where data ownership matters
- Domain-specific software with narrow, knowable scope
- Creator-operations tools for recording, streaming, command control, or review
Usually not Tenra
- General marketing websites or basic online presence work
- Large platform ideas before the real workflow is understood
- AI wrappers where the only feature is sending prompts to a model
- Open-ended projects with no defined operator, data boundary, or handoff path
Budget reality
Tenra does not publish software packages because the cost depends on the operators, data boundaries, integrations, risk, and handoff requirements. The first decision is fit; pricing follows a defined scope.
Focused software work
Custom software is scoped after fit, but focused internal tools, local-first utilities, and prototypes should usually be treated as five-figure projects.
Larger operational systems
Systems with integrations, data migration, permissions, AI constraints, desktop packaging, or long-term workflows are estimated after definition.
Need to ask about a fit?
Send a concise description of the system, the operators, the current stack, and the constraints. If the project belongs here, we'll continue the conversation. If it belongs elsewhere in the suite, we'll say so plainly.