ParalineCapability status
Understand which parts of Paraline are available today and which describe the product direction.
Paraline’s documentation explains both the current product experience and the larger system being built. This page makes the difference explicit.
That distinction matters for any business evaluating software. A clear architecture can show where a product is going, but it should not be mistaken for a feature, integration, security control, or service guarantee that is already available.
How to read the status labels
| Status | Plain-language meaning |
|---|---|
| Available | You can use the capability now within the documented public boundary. |
| Prototype | The idea has been demonstrated, but it is not a supported production commitment. |
| Planned | Paraline intends to build it, although the name, interface, or behavior may change. |
| Concept | The page explains a product principle or longer-term architecture rather than a released feature. |
A status applies to the specific capability being discussed. One article may combine an available documentation experience with a planned runtime interface.
Current product boundary
| Area | Status | What that means today |
|---|---|---|
| Public website | Available | The Paraline marketing and education experience is live. |
| Documentation | Available | The current documentation, navigation, and search experience can be used publicly. |
| Contact workflow | Available | Visitors can submit an inquiry through the public form. |
| Interactive demonstrations | Prototype | Demonstrations can validate an experience but should not be treated as the complete production runtime. |
| Workspace operating layer | Concept | The architecture and operating principles are documented as the product direction. |
| Native agent execution | Planned | A stable public agent runtime has not been released. |
| Workflow and approval engine | Planned | Durable execution, retries, waiting, and approval interfaces remain design material. |
| Imports and synchronization | Planned | Production connector and mapping behavior is not yet a public capability. |
| MCP server and client | Planned | Public, versioned resources, tools, scopes, and authorization are not yet released. |
| Public API and SDK | Planned | Examples illustrate the intended developer experience rather than stable interfaces. |
What examples do—and do not—promise
Examples are used throughout the documentation because concrete situations are the best way to explain the product model. A sample workflow, code block, tool name, or data schema shows how Paraline is intended to work.
It does not become a released interface unless the page identifies a version, configuration requirements, limits, failure behavior, and an available status.
Likewise, mentioning an external service does not claim that a production connector exists. Describing a security architecture does not claim a certification or regulatory guarantee.
Questions to ask before relying on a capability
Before planning a production implementation, confirm:
- Is the capability marked available?
- Is there a stable version or documented interface?
- Are authentication, permissions, limits, and failure behavior defined?
- Is the required integration actually supported?
- Are the relevant security and service commitments documented?
If those answers are not present, treat the material as product direction and use it for evaluation or design—not as a production guarantee.
Describe the future honestly
Product vision should be detailed enough to evaluate while remaining clear about what has and has not been released.