Mulberry leaves, silk fibre and cocoons

Sericulture operations, connected

The connected platform for modern sericulture

SeriFlow is being developed for producers, cooperatives, laboratories, buyers and regional programmes that need batches, field work, quality evidence, procurement and traceability to stay connected.

Multilingual Offline-aware API-ready

A connected operating layer

Keep the systems that work. Connect the evidence that matters.

SeriFlow is designed to sit around real workflows rather than demand a wholesale replacement. Where suitable interfaces exist, agreed records can move through documented APIs, webhooks or governed file exchange.

The integration boundary stays visible: identifiers, units, roles, data ownership, failure handling and support limits are agreed before implementation.

REST / OpenAPIWebhooksCSV / XLSXOIDC / OAuth

Scroll through one connected record

Watch a batch record gain context as the work moves forward.

Each step adds evidence to the same history instead of starting another disconnected file.

01

Egg lot

Supplier identity, certificate, hatch window and accountable owner.

02

Mulberry readiness

Orchard, variety, harvest window and field-quality checks.

03

Rearing

Stages, tasks, conditions, observations, exceptions and approvals.

04

Cocoon lot

Receipt, source rearing, sample, measurements and grading evidence.

05

Settlement

Accepted quantity, pricing-rule version, approval and export status.

06

Provenance

A permissioned QR view carries the recorded history forward.

Operational coverage

One record, many operational views.

Each participant sees the part they are responsible for, while approved identifiers keep the wider chain connected.

01

Plan and rear

Egg lots, hatching, mulberry readiness, stages, tasks and exceptions.

02

Prove quality

Sampling method, source image, measurement, reviewer and rule version stay together.

03

Procure and settle

Cocoon intake, accepted quantity, grading decisions and approved exports.

04

Trace and report

Permissioned provenance, programme reporting and QR-linked public views.

APIs and existing systems

Integrate where an interface exists — without forcing replacement.

Where a client platform exposes a documented API, webhook or agreed export, SeriFlow can map identifiers, units, roles and ownership into a controlled integration.

OpenAPI Initiative
Existing environment
  • ERP / MIS / LIMS
  • Field apps and spreadsheets
  • Sensors and data loggers
  • GIS, BI and document stores
SeriFlow integration boundary
  1. 1DiscoverSystems, owners and support limits
  2. 2MapStable IDs, units and code lists
  3. 3ValidateRequired fields, permissions and audit
  4. 4OperateRetries, monitoring and change control
Documented surfaces
Record APIs
Batches, rearing, orchards and evidence
Events / webhooks
Status, approvals and exceptions
File exchange
CSV/XLSX, SFTP
Identity
OIDC / OAuth 2 / SAML

No open API? Start with governed CSV/XLSX exchange or a scoped connector.

Examples to evaluate per deploymentNot a fixed stack
Keycloak logo
Identity & SSO
Node-RED logo
Integration flows
Mosquitto logo
Sensor messaging
Apache Superset logo
Downstream BI

Candidate components are selected per implementation after security, support, commercial-term and licence review. References do not imply partnership or endorsement.

Product direction — currently under development

Start with one real workflow.

Map the existing systems, agree the evidence, test the integration boundary and prove operational value before expanding the platform.

Discuss a technical pilot