Custom Nextcloud apps
We build interfaces, rules, metadata and actions that respect platform permissions, conventions and release lifecycle.
Nextcloud development
We develop apps inside Nextcloud and integrate it with ERP, CRM, portals, identity providers and document services. We start with the process, use supported extension points and APIs, and manage the lifecycle with the platform.
Sustainable integration
An integration must establish which system is authoritative, how people and documents are identified, what happens to errors and duplicates, and who may retry an operation. Without those decisions, synchronisation hides inconsistencies instead of removing them.
We use Nextcloud extension mechanisms and interfaces such as WebDAV, CalDAV, CardDAV and available APIs when suitable. We avoid core patches and undocumented coupling. Code, configuration, migrations and dependencies enter the same testing, release, observability and update process.
What we build
The solution may be a small automation, a complete app or a workflow distributed across several systems.
We build interfaces, rules, metadata and actions that respect platform permissions, conventions and release lifecycle.
We connect document events to validation, assignment, notification and business steps with observable states and errors.
We exchange master data, cases, documents and references without indiscriminately duplicating data or authorisation.
We integrate identity, groups and revocation through compatible components while preserving service and emergency accounts.
We automate import, metadata, structure and permissions with reconciliation and reporting for items that were not transferred.
We maintain supported versions, automated tests, staging environments and upgrade plans for apps and dependencies.
Engineering method
Every integration has a data owner, a contract and defined behaviour when something fails.
We define authoritative systems, identity, permissions, volumes, acceptable latency, errors and audit requirements.
We assess apps, APIs, protocols, events or queues for supportability, security, compatibility and maintenance.
We use separate environments, test data, code review and proportionate functional, security, migration and load tests.
We version changes and dependencies, enable logs and metrics, and test Nextcloud upgrades before production.
Upgradeability as a requirement
We favour documented contracts and extension points. If a capability requires a compromise or relies on an interface with limited guarantees, we make the risk, required testing and exit strategy explicit before implementation.
Frequently asked questions
Yes, where the systems expose dependable interfaces or allow a controlled connector. We first define authoritative data, identifiers, permissions, frequency, error handling and reconciliation, then select appropriate APIs, events or batch processes.
Yes. We can build apps with interfaces, rules and integrations that follow the Nextcloud architecture. Scope, distribution, licensing, supported versions and maintenance responsibility are agreed with the customer.
We maintain a compatibility matrix and test apps, migrations and integrations in a separate environment. If a new release introduces incompatible changes, we plan the adaptation before it reaches production.
We define ownership, licensing, repositories, documentation, credentials and export contractually. We design an exit path so that data and operations do not depend on knowledge that cannot be transferred.
Nextcloud is a registered trademark of Nextcloud GmbH. Nebulas Software provides independent consulting, development and managed services; available functions depend on the agreed edition, apps and architecture.
Integration project
Show us the systems, manual hand-offs and duplicated data, and we will identify the simplest maintainable boundary.
Talk to the software team