fin-hub/docs/raas-mvp-packaging.md
tegwick 1abbbe85e4 Implement fin-hub T24-T26: ingest, runway, coupling, RaaS packaging
Add CSV importers, runway calculator, budget alerts, cross-hub coupling
emitters, finhub CLI, and raas-mvp-packaging docs with full test coverage.
2026-07-08 00:59:39 +02:00

66 lines
No EOL
3.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Railiance-as-a-Service — MVP Packaging (CUST-WP-0025-T26)
Status: draft v0.1 (2026-07-08)
## Tier Matrix
| Capability | Self-hosted | Managed | Fully operated |
| --- | --- | --- | --- |
| k3s + GitOps templates | ✓ OSS | ✓ | ✓ |
| Observability (metrics/logs/traces) | docs | ✓ | ✓ |
| Backup + restore drill evidence | customer-run | quarterly | monthly |
| Incident response | community | business hours | 24×7 option |
| FOS hub setup (dev/ops/fin) | docs | dev+ops | full federation |
| Runway/cost dashboard | — | optional add-on | ✓ |
| SLA | best effort | 99.5% monthly | contractual |
## Landing Page Content (Draft)
**Headline:** Sovereign DevOps for EU SMEs — without vendor lock-in.
**Subhead:** Railiance-as-a-Service packages reproducible Kubernetes operations,
observability, and FOS-aligned governance so your team can focus on product work
instead of founder-only ops.
**Proof points:**
- EU-hostable infrastructure with documented restore drills
- GDPR-conscious operations model (data stays under your control)
- VSM-based coordination — not another opaque SaaS dashboard
- Open-core templates; no mandatory hyperscaler control plane
**CTA:** Book an architecture review → scoped managed cutover proposal.
## Onboarding Workflow
1. **Discovery call** — scope workloads, compliance constraints, team size.
2. **Architecture review** — map domains, hubs, and OAS substrate requirements.
3. **Provision** — deploy k3s cluster (Railiance-managed or customer-owned).
4. **GitOps baseline** — ArgoCD apps, secrets custody via OpenBao path.
5. **Observability** — Grafana/Loki/Tempo (or customer-preferred stack).
6. **Restore drill** — execute and capture evidence within 14 days of go-live.
7. **Hub registration** — register repos in dev-hub; ops evidence on Core Hub.
8. **Handover** — runbooks, access model, escalation contacts.
## Legal and GmbH Framework (Draft — Not Legal Advice)
| Topic | v0.1 posture |
| --- | --- |
| **Entity** | Pre-revenue consulting may invoice as founder/freelance; GmbH formation triggered at €10k annual revenue or first managed customer (see bootstrap-protocol). |
| **Liability** | Managed tier: liability capped at 12 months fees; exclude indirect/consequential damages; customer maintains data custody. |
| **SLA** | Managed: 99.5% control-plane availability monthly; credits capped at 25% monthly fee. Fully operated: negotiable. |
| **Data processing** | DPA required for managed/operated tiers; subprocessors listed in canon. |
| **Insurance** | Cyber/liability policy review before first external managed customer. |
## First Customer Acquisition Strategy
1. **Internal dogfood** — complete Railiance restore drill + fin-hub runway evidence.
2. **Founder network** — 3 architecture review offers to EU technical SMEs with DSGVO pressure.
3. **Consulting wedge** — fixed-scope "sovereign ops assessment" (25 days) leading to managed tier.
4. **Content** — publish restore-drill case study (non-secret evidence only).
5. **Partners** — EU hosting/legal partners for GmbH + DPA handoff.
## References
- `the-custodian/canon/projects/railiance/business-model-canvas_v0.1.md`
- `the-custodian/canon/constitution/bootstrap-protocol_v0.1.md`