Production services · Unified administration
Faiber Manage
Operate every enabled service from one project-aware control surface.
Faiber Manage is deployed once as a platform service and opens each service's administration in signed project context, avoiding a separate admin application in every sandbox.
01
Feature map
The production behaviors this service owns, expressed as concrete product features instead of generic modules.
Project-aware navigation across enabled services
Server-side proxying to sandbox service APIs
One optimized administration deployment for the platform
02
Best-fit products
Unified service administration
Operate every enabled service from one project-aware control surface.
Multi-project operations
Operate every enabled service from one project-aware control surface.
Secure project-context handoff
Operate every enabled service from one project-aware control surface.
03
Operational gains
One admin surface
Faiber Manage is deployed once as a platform service and opens each service's administration in signed project context, avoiding a separate admin application in every sandbox.
Less per-sandbox overhead
Faiber Manage is deployed once as a platform service and opens each service's administration in signed project context, avoiding a separate admin application in every sandbox.
Consistent project context
Faiber Manage is deployed once as a platform service and opens each service's administration in signed project context, avoiding a separate admin application in every sandbox.
04
Connected services
Production wiring
How it runs in a Faiber project
Faiber runs this as a shared platform capability. Signed project context connects each enabled project to the same administration surface without duplicating the workload in every sandbox.
API boundary
Application code uses the service API or typed SDK contract. Identity, permissions, tenant scope, and project context stay explicit at every read and write boundary.
Manage-ready operations
Faiber Manage opens this service beside the rest of the enabled stack, so teams can inspect records, adjust settings, review health, and ask the Manage agent for guided service changes.
Open LMS, Payments, and Messenger for this project and summarize what needs attention.
Technical reference
infera-manageInternal API port: 8095These values support deployment wiring. Product code should use configured endpoints or SDK clients, not hard-coded internal addresses.
FAQ
Questions teams ask before enabling it
What does Faiber Manage add to a Faiber application?
Faiber Manage is deployed once as a platform service and opens each service's administration in signed project context, avoiding a separate admin application in every sandbox.
How is Faiber Manage provisioned?
Faiber provisions it once in the platform namespace. A signed project handoff supplies the active project and enabled-service context without duplicating the management application in each sandbox.
Can Faiber Manage be used with an existing frontend?
Yes. Faiber Manage exposes a defined API surface and can be integrated from an existing React application or a new Faiber project.
Faiber
Provision the capabilities your product actually needs.
Start with a real project, select services explicitly, and keep code, access, deployment, and operations connected.