ID
Unified identity and access
One organization model, predictable roles, product permissions, API credentials, and account administration across the suite.
The platform beneath every product
Simple for teams. Serious for developers.
Feradel pairs focused software interfaces with a consistent platform for identity, permissions, events, usage, integrations, and application development.
Shared foundations
Seven products should feel like one deliberate system.
The platform layer creates consistency without flattening the specialized workflows that make each product useful.
API
Consistent developer experience
Shared authentication patterns, resource conventions, errors, pagination, idempotency, rate-limit headers, and SDK opportunities.
↗
Events and webhooks
Respond to the work happening in Feradel products with signed, retry-aware event delivery and searchable webhook history.
◎
Usage you can understand
Product-specific meters roll into one administrative view, with clear thresholds and predictable behavior at plan limits.
7
Modular by design
Adopt the product that solves today’s problem. Add another when a connected workflow earns its place. Product tiers remain independent.
1Feradel account
7Focused products
5Plan sizes each
A predictable API surface
Build once. Recognize the pattern everywhere.
A developer who has integrated one Feradel product should immediately understand the next: the same authentication, resource style, metadata, webhook envelope, and usage headers.
Open documentation// Shared response conventions across products { "data": { ... }, "meta": { "requestId": "req_01...", "product": "ferasign", "usage": { "used": 42, "limit": 100, "resetsAt": "2026-08-01" } } }
Visitor messageFeraChat
Lead createdFeraMatters
ConsultationFeraCal
Intake completedFeraSurvey
Agreement generatedFeraRender
Request deliveredFeraEmail
Agreement signedFeraSign
Example connected workflow
From website visitor to signed client.
A conversation can become a lead, an appointment, a completed intake, a rendered agreement, a delivery request, and a signed client—without requiring the team to copy information between unrelated systems.
✓
Shared context
Carry identities and references through connected product events.
✓
Loose coupling
Use webhooks and APIs rather than locking workflows into a single monolith.
✓
Visible automation
Let users understand what happened and recover when a step needs attention.
Start with the product you need.
The shared platform is already underneath it.