For customers¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
Outcomes¶
- Work gets done by agents you can trust: every run has a scope, a budget and a trail; nothing reaches your repositories, environments or external systems without a classed action and, where it matters, a person's decision on the exact proposal.
- Products get built from proven parts: the same templates, identity, tenancy, billing and observability ConnectSoft runs in production, generated from blueprints with provenance to every file (examples).
- Products get operated: under a managed edition ConnectSoft keeps objectives, rolls out upgrades in waves, runs the incident desk and off-boards with your data handed over first (product fleet operations).
- What you learn stays yours: assets, knowledge, memory and evidence are tenant-scoped; the models underneath are profiles you can change (data governance).
How work is done¶
sequenceDiagram
participant You as Requester
participant F as Factory
participant R as Reviewer
You->>F: submit a run (scope, published agent release, limits)
F->>F: agents work in sandboxes with classed tools
F->>R: approval requested for a gated action (exact version)
R->>F: decision
F-->>You: artifacts with lineage, usage by status, evidenceThe seven roles — requester, reviewer, asset maintainer, operator, workspace admin, platform admin, observer — are yours to assign; separation of duties is enforced, not recommended (personas and journeys).
What a generated product looks like¶
A product is services per bounded context on ConnectSoft's clean-architecture template, its own gateway, identity through the Authorization Server, tenants, editions, entitlements, billing and metering from the SaaS foundations, Pulumi infrastructure and pipelines — in your region, with your classification and retention rules (Generated SaaS). The examples show twenty-nine verticals.
Editions and managed operations¶
| Edition of the Factory | Covers |
|---|---|
| Internal budget control | your own teams and budgets, no invoicing |
| Usage-based | runs, tokens and operated instances metered and billed |
| Seat and edition plans | per-user plans with entitlements |
| Managed edition of a product | ConnectSoft commits to |
|---|---|
| Self-operated | inventory and upgrade offers |
| Managed | standard objectives, rollouts, incident desk |
| ManagedPlus | stricter objectives, on-call, faster acknowledgement |
See the commercial model and the NFR baseline for the numbers.
Your data¶
Region selected per tenant; data classified; no raw prompts or responses logged by default; audit kept seven years redacted; everything exportable in open formats; deletion within the window with every store's receipt (data governance, retention and residency).
Starting¶
A project is onboarded by a workspace admin under the tenant's policy; the first run is an assessment of your repository or a vision blueprint for a new product (onboard a project, submit an assessment).