Answers to the questions prospects ask first.

Two things, decoupled. (1) The FCC Platform — a multi-tenant SaaS for SAP basis monitoring, alerting, automation, and audit. (2) AWS Reseller — we sell AWS to companies running SAP and design / operate the landing zones. Most customers use one. Many use both.

MSPs running SAP for multiple customers; in-house Basis teams of 2–20 people; and security / SOC analysts who need an indexed audit trail across the estate. Service desks get a read-only view that's good enough to triage without touching production.

NetWeaver 7.x, S/4HANA, BW/4HANA. Database side covers HANA (with SYSTEMDB + tenant detection), MaxDB, Oracle, MSSQL. The agent runs on RHEL, SLES, and Ubuntu.

Yes. We set up a sandbox tenant against one non-production SID, typically a 14-day PoC. Production SIDs join later through the same agent — no second install.

No. The agent is outbound-only — it polls Farrenio over HTTPS for its config and pushes metrics the same way. No new firewall rules, no exposed ports on your SAP boxes.

A single Python daemon (~12 MB) running as the sapagent user, sudo-ing to <sid>adm for SAP commands. systemd unit, /etc/fcc-agent/config.yaml, signed auto-update tarballs.

Negligible. Steady-state CPU < 1%, < 100 MB RAM. Network traffic averages 2 KB/s per agent. The default polling interval is 60 s for metrics and 5 min for SM37 / heavyweight transactions.

Fleet management UI — pick agents, click "Update". Or enable auto-update on each agent and we push signed tarballs at the cadence you configure (default daily).

JWT (HS256, 24 h expiry). MFA enforceable per role; the code-server gate always requires TOTP. Google OAuth as an alternative path — new Google sign-ins are held in a pending state until a platform owner approves them.

69 individually-toggleable permissions across 6 roles: platform_owner, admin, customer_admin, customer, technician, service_desk. Plus a marketing-only support_agent role for Aria chat operators. Every menu, every action, every tab — overrides editable from the Role Management UI.

Yes. The service_desk role is read-only on alerts and incidents — no SAP transaction access, no config changes, no token reveal. You can carve out exactly what each team sees.

Every login, role change, token reveal, runbook execution, sapcontrol command, and configuration change is appended to db.audit_logs with operator id, target, IP, user-agent, and the action's full delta. Default retention 180 days, configurable up to 365.

Open /security — a dedicated page that lays out auth, RBAC, encryption, audit, vulnerability management, and compliance.

Per-SID, transparent, no hidden seats. Talk to us with your actual inventory (production + lower environments) and we'll size a tier to your estate. Tiers are Starter (up to 5 SIDs), Business (up to 25), Enterprise (unlimited).

Yes — annual gets a discount. Monthly is fine for PoCs or short engagements.

Each unique SAP system identifier across PRD / QAS / DEV / sandbox. HANA tenants on the same SYSTEMDB count once.

No. AWS resale and the monitoring platform are decoupled — many customers use one without the other. They're cheaper together but never bundled-or-nothing.

Yes. Farrenio is a registered AWS Reseller in the AWS Partner Network. We can show partner status on request and consolidate billing under our account.

0%. AWS list price, billed monthly by us. We earn from the platform subscription and consulting hours, not from compute margin.

Wherever AWS does. Default is eu-central-1 (Frankfurt) for EU customers; we'll design around your data-residency constraints. The FCC Platform itself is EU-hosted.

We honestly tell you when RISE is the right call and when it isn't. We'll design an EC2 / HANA landing zone that lives next to RISE where that makes sense, and skip it where it doesn't.

Yes. SSH credentials, SMTP passwords, OAuth refresh tokens, and API tokens are sealed with Fernet keys derived from JWT_SECRET. Agent-side credentials use a host-local Fernet key with an "enc:" prefix.

Opt-in only — events only fire when the visitor has accepted the Analytics cookie category. IPs are stored truncated to /24. Anonymous pageview counts use a daily-rotating sha256 bucket that can't be reversed to a visitor and resets every midnight.

Chat sessions and demo requests can be deleted by the platform owner. Analytics events expire automatically after 180 days. Audit logs follow the configured retention (180–365 days).

Yes — DPA template available on request. Email contact@farrenio.com.

A small AI assistant at the bottom right of the marketing site. Answers questions about the platform, pricing, security, and onboarding. Asks visitors for their email + name when they want to take the conversation further.

Yes. Operators with the support_agent role (or platform_owner / admin) can step in from the in-app Chat Sessions page. Visitors see a green "Agent online" pill when a human is on shift.

Transcripts are persisted in the Farrenio backend for 180 days so platform owners can review intent patterns and follow up. Visitors can request deletion at any time.

A 30-minute scope call and one production SID is usually streaming live metrics within an hour of agent install. The rest of the landscape follows as fast as you can roll out the package.

Community support on Starter, business-hours email on Business, 24/7 + SLA credit on Enterprise. All tiers have access to the documentation and the audit-trail self-service.

Email contact@farrenio.com with "[SECURITY]" in the subject. We acknowledge within one business day and coordinate disclosure responsibly.

The /changelog page lists releases in reverse-chronological order with the items each one shipped. /status is the live platform health board.