Internal tools
Panels to manage requests, inventory, tickets or tasks, with role-based permissions, change history and connections to your tools through APIs or n8n.
Nexura Digital service
Custom web app development and PWAs, only when it pays off
Some processes aren't handled well by any tool on the market, and others are. We help you tell them apart and, when it pays off, we build the app that fits the way you work.
We build custom web apps and PWAs: internal tools, portals where your customers check orders or documents, and booking systems that run in the browser and install on a phone. They're for companies whose process doesn't fit an off-the-shelf tool or that need to connect several. You start with the 7-day trial by building a small first module.
What we build
Client portals
A private login where your customers check their order status, download documents, open tickets or approve quotes without sending an email.
Booking systems
Appointments, rooms, equipment or spots with your own rules, such as availability per person, deposits through Stripe or email reminders, when a standard calendar falls short.
Off-the-shelf tool or custom development?
An off-the-shelf tool is better if
- Your process is common and something like Calendly, Microsoft Bookings, Shopify or Airtable covers it.
- You haven't validated the process yet; a spreadsheet or no-code tool teaches you more, sooner.
- Nobody will look after the app once it launches.
Custom pays off if
- The process is part of what sets you apart, and the tools force you to change it.
- You need data from several systems on a single screen.
- You have many occasional users and per-user licenses stop making sense.
PWA or native app?
A PWA runs in the browser, installs on the home screen and can show content offline; on iPhone, push notifications require iOS 16.4 or later and adding it to the home screen. If you need Bluetooth, NFC, background processes or an App Store listing, consider a native app.
What you get and who owns the code
What's delivered
- The app in production, on hosting in your name.
- The code repository, for example on GitHub, with admin access for you.
- Technical and user documentation, including how to deploy changes.
- Backups set up and tested.
Code ownership and maintenance
We propose that code, domain and hosting be in your name from day one, and we put it in writing. After launch, the app needs security updates and small improvements: you can hire that maintenance from us or hand it to another team, thanks to the documentation.
Phased development
Something usable early, without skipping steps
- We map the real process, users and data with the people who live it every day.
- A clickable prototype of the key screens, tested before coding starts.
- Module-by-module development with widely used technologies, such as React or Next.js and PostgreSQL.
- Testing with real users before opening the app to everyone.
- Go-live, documentation and training for your team.
How to start: a first module in 7 days
Small, real and validated
In the trial we pick one concrete piece, such as the booking request form with its review panel, and build it so real people can use it. If the project is large, the alternative is a clickable prototype with its scope document. All of it with scope, dates and terms agreed in writing beforehand; see /en/7-day-trial/.
FAQ
Frequently asked questions
Who owns the code?
Our proposal is that you do: the repository is created in your account or transferred to you, and hosting and domain are in your name. We put this in writing before we start, along with the licenses of any third-party libraries, which keep their own terms.
Can I publish the PWA on the App Store and Google Play?
A PWA installs from the browser without going through any store. Google Play accepts PWAs packaged with Trusted Web Activity. The App Store is stricter: Apple may reject apps that only wrap a website. If being in the stores is a must, we assess it at the start, because it changes the technology to choose.
What if I want to switch providers later?
We use widely adopted technologies and document the architecture, deployment and key decisions so another team can pick up the work. If, as we propose, the repository and hosting are in your name, switching doesn't depend on us handing anything back.
Can it connect to the tools we already use?
Usually, yes, if the tool has an API: Google Workspace, Microsoft 365, Stripe, your ERP or your CRM. For multi-step connections, n8n is sometimes simpler; the automation then runs on a server you pay for, n8n Cloud or your own VPS, included in the quote.
Contact
Off-the-shelf or custom? Let's work it out together
Tell us which process you want to digitize and what you use today. We'll tell you frankly whether a market tool is enough or custom development pays off.
Tools
Find out where to start in one minute.
Tools
What do you want to improve?
Pick a goal and we'll suggest the services that fit best.