Connected
Control plane
A single middleware layer for AlinPortal, AlinCargo, and third-party merchants or vendors.
Next.js
TypeScript
shadcn-style UI
Local store
Control plane
A single middleware layer for AlinPortal, AlinCargo, and third-party merchants or vendors.
Payments
1
1 need action or provider follow-up.
Integrations
3
2 connected.
Sync records
0
Inbound cargo and portal payloads normalized in one store.
Webhooks
0
Signature-verified event trail across vendors and providers.
Live posture
Current connections, active routes, and decommission guardrails.
AlinPortal
https://app.alin-group.com
connected
Auth: insforge-auth · Last seen just now
AlinCargo
https://app.alin-group.com
connected
Auth: bearer · Last seen just now
Sample Vendor
https://vendor.example.com
degraded
Auth: signed-webhook · Last seen N/A
Decommission rule: keep Alin API and Cargo API live until this control plane can serve all traffic, backfill the data model, and pass a parallel-run soak period.
Latest activity
Recent events and seeded operational state.
No audit events yet. New payments, syncs, and webhook calls will appear here.
Payments snapshot
Sample provider-neutral payment model.
| ID | Provider | Status | Amount | Updated |
|---|---|---|---|---|
| pay_demo_1 | maya | requires_action | ₱150,000.00 | Jun 21, 2026, 1:24 PM |
Next actions
What the middleware should absorb next.
Port sync receiver flows from cargo and portal.
Replace local persistence with InsForge tables and auth.
Expand the API playground with imported collections and environments.
Cut over merchants and vendors after parallel-run validation.