Nextcloud development

Nextcloud can become part of your software, not another island.

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

The goal is not to connect two APIs. It is to keep work coherent.

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

Functions inside the platform and connections beyond it.

The solution may be a small automation, a complete app or a workflow distributed across several systems.

01 · Applications

Custom Nextcloud apps

We build interfaces, rules, metadata and actions that respect platform permissions, conventions and release lifecycle.

02 · Processes

Workflow and automation

We connect document events to validation, assignment, notification and business steps with observable states and errors.

03 · Systems

ERP, CRM and portals

We exchange master data, cases, documents and references without indiscriminately duplicating data or authorisation.

04 · Identity

SSO and provisioning

We integrate identity, groups and revocation through compatible components while preserving service and emergency accounts.

05 · Content

Migration and classification

We automate import, metadata, structure and permissions with reconciliation and reporting for items that were not transferred.

06 · Lifecycle

Testing and compatibility

We maintain supported versions, automated tests, staging environments and upgrade plans for apps and dependencies.

Engineering method

Extend without compromising upgrades.

Every integration has a data owner, a contract and defined behaviour when something fails.

  1. Control 01

    Design process and ownership

    We define authoritative systems, identity, permissions, volumes, acceptable latency, errors and audit requirements.

  2. Control 02

    Choose the extension point

    We assess apps, APIs, protocols, events or queues for supportability, security, compatibility and maintenance.

  3. Control 03

    Build and verify in isolation

    We use separate environments, test data, code review and proportionate functional, security, migration and load tests.

  4. Control 04

    Release and observe

    We version changes and dependencies, enable logs and metrics, and test Nextcloud upgrades before production.

Upgradeability as a requirement

We do not modify core for a quick but fragile result.

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

Clear answers before we define the scope.

01Can you connect Nextcloud to our ERP or CRM?

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.

02Do you build apps that run directly inside Nextcloud?

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.

03What happens to custom apps during an upgrade?

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.

04Do customers retain access to their data and code?

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

Connect Nextcloud to where the work actually happens.

Show us the systems, manual hand-offs and duplicated data, and we will identify the simplest maintainable boundary.

Talk to the software team