TECHNOLOGY & ENGINEERING
A good system connects the screen people use to the records, workflows and infrastructure behind it. Explore what our tools do, where we use them and how we approach the difficult requirements.
TOOLS WITH A CLEAR PURPOSE
The choice depends on the product’s users, records, integrations and operating needs. Our products share engineering practices while using different combinations of tools.
Web and interface engineering
Help customers and colleagues complete their work in a browser.
Server-rendered content, authenticated workspaces, reusable interfaces and responsive product experiences. Metadata, image delivery and readable interaction states are part of the implementation.
Backend and operational systems
Keep clients, work, permissions and operational records connected.
APIs, business records, asynchronous work and data relationships. The choice follows the operational workflow and integration needs rather than a single stack applied to every system.
AI and document workflows
Use business information to answer questions and prepare work for review.
Model capabilities are connected to approved knowledge, customer context and permitted actions. Review and human handover are designed around the business's decisions.
Mail and interoperability
Give a team company-domain email that can work with compatible clients.
Mail access, calendar and contact interoperability, and domain authentication are distinct responsibilities. Supporting them makes the workspace useful beyond one browser interface.
Mobile and real-time interfaces
Bring messages, tasks and customer information to connected interfaces.
Connected mobile screens, streaming replies, conversations and notifications need explicit session, reconnect and failure behavior. Public app availability is confirmed separately.
Cloud, storage and delivery
Provide the deployment, storage and access model a workload needs.
Deployment and access control are part of the system. Oneemail's documented Drive architecture uses S3 and KMS; infrastructure for other workloads follows their actual requirements.
Geospatial rendering
Help users move between a mapped location and the information behind it.
OneeGIS powers Sakhejung’s map, connecting records, imagery and geographic interaction. We keep the available source and observation context visible rather than implying all layers are equally current.
Search and media pipelines
Make information searchable and prepare video for adaptive playback.
Search systems need indexing and useful retrieval behavior; media systems need coherent processing and delivery pipelines. These tools serve different workloads within our engineering work.
Elasticsearch discovery work and OneeStream’s media pipeline.
THE ENGINEERING IN DETAIL
Follow the workflow first. Expand an example to read the requirement and the implementation approach, then explore the product where that work appears.
Oneemail
A team can use its business identity across supported mail and collaboration tools.
Email has to work across domain ownership, sender authentication, mailbox behavior, client interoperability and organizational access. A polished inbox is only one part of that work.
Oneemail connects mailbox workflows, administrative controls, migration, mail health and collaboration. JMAP-backed browser work and compatible mail and sync protocols help the system fit the tools organizations already use.
OneeAI
Customers can continue the conversation without starting their explanation again.
A reply can stream while a customer is verified, a tool is working or a staff member takes over. Losing context or replaying a request at a handoff can create more work than the assistant saves.
The Sakhejung implementation connects streamed replies, stored turns, business knowledge, customer context and staff-aware handover. Failures and waiting states are shown instead of hidden behind an endless typing indicator.
Oneesys & OneeCRM
The same record scope needs to hold when a person browses, searches or downloads a file.
A sensitive file must follow its permission rules in the folder tree, search, linked records and download path. Hiding a button is not enough to protect the document.
The business-software implementation applies document and folder restrictions across its surfaces. Stored credentials are a separate concern, with encrypted values and deliberate, recorded reveal actions.
Oneesys
A person can check extracted values against the original document before confirming them.
A date, taxable value or total extracted incorrectly from a scan can affect a register. A system needs a visible verification step before turning a model's output into an operational record.
Oneesys holds extracted bill data as drafts, shows field confidence and cross-checks arithmetic. People confirm the result; local-calendar dates are rechecked against the source text.
OneeCRM & Oneesys
Teams can connect fiscal periods, deadlines and recorded submissions to the right working dates.
A Nepali fiscal period is an operating rule, not simply an English label on a Gregorian calendar. Filing frequencies, payroll periods and recorded submissions need consistent dates.
The implementation works with Bikram Sambat fiscal schedules and explicit period states. Draft work, review, filing references and locked records keep the workflow understandable and accountable.
OneeGIS
Users can understand the selected plot alongside its records, sources and observations.
A plot register, geometry, imagery and observation layers describe related things with different sources and dates. They need to remain connected as users search, select and move around the map.
OneeGIS powers Sakhejung’s map, combining MapLibre rendering, mapped boundaries, a searchable register, imagery switching and layer context. Source and observation information help users interpret the view.
OneeCRM & collaboration systems
Messages and task updates should stay connected to stored records when devices or connections change.
Messages, notifications, task states and customer records must remain consistent across devices, interrupted connections and role-specific views.
Next.js web workspaces and Flutter mobile implementation share operational backend models. Conversation and notification flows retain stored records and show recoverable failures.
OneeStream
The player can select an available quality variant and continue viewing within the configured access model.
A streaming experience spans file processing, encoding variants, packaging, protected delivery and a player that adapts to the connection.
Our demonstration systems include FastAPI orchestration, FFmpeg GPU-assisted encoding, DASH/HLS packaging and adaptive playback. OneeStream adds resume and continue-watching behavior.
OneeSheet
People need to know what was calculated, saved and approved, even when a workbook changes.
A formula-driven workbook must retain its dependencies, recover acknowledged edits and preserve the exact figures reviewed.
OneeSheet combines a sparse C# engine, a WebAssembly worker, canvas rendering and SignalR collaboration. Our development adds checksummed journals, reusable data refresh and preserved approval records.
DESIGNING FOR EVERYDAY OPERATION
Access, review, recovery and operation are part of the architecture. The checks follow the actions and records that matter to each system.
Keep actions, versions and status changes connected to the information they affect. A person should be able to understand what happened.
Make extracted data and AI-driven next steps visible at the right confirmation point. Financial and access decisions retain human responsibility.
Plan role and record scope, then check the underlying resource in viewing, search and download paths.
Prepare deployment, monitoring, recovery behavior and maintenance. Production checks follow the actual deployment environment.