Oryon expertise
Custom applications and software
Software that fits your business, designed with you, documented and maintainable.
Based in Givors · Rhône area and remote support across France · Project discussions in French
Shaped around your business.
How can we build an application around our business processes?
Custom development turns a small business’s processes into an application: interface, business logic and data. The work starts with approved specifications and includes tested versions, deployment and handover documentation. The quote defines the features and deliverables.
A project in context
In use · Testing ongoing
Tattoo Station: a local AI application
A custom application bringing together design preparation, variations and retouching, running entirely locally and offline on NVIDIA AGX Orin.
Status on 1 October 2026: the solution is in use at the client’s premises and available to its customers. Testing continues.
Read the project Tattoo StationWhat you receive
- A custom web application: interface, business logic and database
- Specifications agreed together before development
- Documented source code delivered to your repository
- A documented maintenance and handover plan
What this brings you
- A business process that runs without workarounds
- Ownership of the code, with freedom to change providers
- Documentation that enables another team to take over
- Targeted improvements quoted in advance
When can Oryon help?
- Generic tools do not follow your processes and waste your time
- Your data is scattered across spreadsheets, emails and disconnected tools
- An existing application can no longer evolve with your business
- You want to replace spreadsheets and manual work with a coherent business tool
How the work progresses
- Discovery workshop: current processes, constraints and measurable goals
- Written specifications approved by you as a contractual deliverable
- Iterative development: working versions connected to your existing tools where needed, then validation with your team
- Acceptance testing, training and getting-started documentation
- Supported deployment, followed by maintenance and improvements
What we need to plan together
- The quality of the specifications shapes the result: allow time for discovery
- Timelines depend on your team’s availability for approvals
- The quote fixes the scope; additional work requires a priced amendment
Details of the work
Scope and deliverables
The application is built around your processes, constraints and the goals established during discovery. The scope can include a web interface, business logic, a database and connections to existing tools.
Written specifications are approved before development. Your team then reviews working versions. Acceptance testing, training and supported deployment prepare the software for everyday use.
Integration and migration
Discovery time and your team’s availability for approvals affect delivery. Technical choices depend on the context and the tools to connect.
The quote fixes the scope. Extra requests receive a priced amendment before work expands; improvements are agreed in advance.
Maintenance and ownership
Documented source code is delivered to your repository. The specifications and getting-started documentation explain the delivered features and technical decisions.
A documented maintenance and handover plan accompanies delivery. Your team or another provider can take over using the supplied code and documentation.
Technologies used
- TypeScript, React / Next.js for interfaces
- Node.js and PostgreSQL for business logic and data
- Other technologies where the context calls for them
Frequently asked questions
What budget does a custom application require?
The budget depends on the processes, features and connections involved. Discovery leads to specifications and a quote defining the scope. Additional needs are priced in an amendment before implementation.
Should we take over the existing software or build a new application?
Discovery starts with your processes and the constraints of the existing application. A takeover begins with reading the code and assessing what can be kept. Features to retain, connect or build are defined before development.
Who owns the application’s code?
You retain ownership of the code, delivered and documented in your repository. Delivery includes getting-started documentation and a handover plan so your team or another provider can continue.
Let’s discuss your context
Send us your current processes, even as rough notes: discovery will structure them.
Based in Givors, in the Rhône area, Oryon supports projects remotely across France. On-site work is considered for each project. Project discussions take place in French.
Complementary services
Continue preparing your project
- Automation
Automating business tasks: choose a first project
A method for choosing a repetitive task, describing exchanges between tools and testing a first automation against concrete criteria.
Read the guide