GoodData typical implementation process:
Initial scoping and planning: Define use cases, users, data sources, security model, and decide between internal analytics vs. embedded/product use; this often fits in a few discovery workshops over several days.
Environment and access setup: Provision GoodData Cloud organization, configure authentication (OIDC/SSO), set up workspaces, and whitelist IPs; typically completed in days for standard SSO scenarios.
Connect data sources: Create data-source connections to warehouses (for example, Snowflake, BigQuery, Redshift) or databases and verify connectivity and basic query performance.
Build initial data pipeline: Follow GoodData’s pipeline phases (preparation, test implementation, production implementation) to design and automate data loading or direct-query models.
Model data and semantic layer: Create logical data models (LDMs), define metrics, hierarchies, and permissions to align with business concepts and multi-tenant needs.
Develop dashboards and insights: Design core dashboards, visualizations, and filters for the first set of users or customers, iterating with stakeholders for fit.
Embed and integrate (if needed): Integrate GoodData into web or SaaS applications using iframes, React components, or APIs and configure user provisioning and tenant mapping.
GoodData is highly customizable across data, analytics, UI, and tenancy layers to fit specific business needs.
Key customization points include:
Custom semantic models, metrics, and hierarchies per business domain.
Tenant-specific workspaces with shared models but isolated data (multi-tenant analytics).
Client-level customization of metrics, insights, and dashboards in each tenant workspace.
Attribute-based data permissions to filter what each user or group can see (for example, by region, branch, or customer).
Flexible role and permission model (VIEW, ANALYZE, EXPORT, EDIT, MANAGE, etc.) controlling who can design or consume content.
White-labeling of domains (for example, analytics.yourcompany.com) and full portal rebranding.
UI theming options for colors, fonts, logos, and component styles to match your product.
Ability to hide GoodData branding, help links, and references for OEM / embedded scenarios.
Multiple embedding methods (iframes, Web Components, React SDK) for custom UX patterns.
Custom dashboard layouts, filters, and visualizations tailored to each role or department.
Custom dashboard plugins to extend functionality with your own components and logic.
API-first configuration for white-labeling, domain settings, and organization-wide options.
Programmatic control of workspace creation, cloning, and segmentation for large multi-tenant estates.
GoodData offers structured training resources plus enterprise-grade support to help new users ramp quickly.
Guided product onboarding via “Getting Started with GoodData Cloud” articles that walk new users through setup, data connection, modeling, and dashboards in about 30 minutes.
GoodData University with self-paced course tracks (for example, Getting Started, Connect Your Data, Designing Data Models, developer tools) focused on both business users and technical teams.
Video tutorials and beginner-friendly walkthroughs on core workflows such as data analysis, visualization, and embedding.
Certification program (GoodData Cloud Professional) that validates skills in architecture, permissions, MAQL metrics, dashboards, and integrations, including exam prep materials.
Central “Learn” hub linking documentation, courses, community, and support so users can choose docs, training, or human help as needed.
24x7 platform monitoring and SLA-backed enterprise support (99.5% availability SLA for enterprise plans), with on-duty personnel handling incidents.
GoodData implements layered technical, organizational, and compliance controls to protect customer data across its cloud platform.
Key security measures include:
Defense-in-depth architecture, covering physical data center security, hardened Kubernetes infrastructure, firewalls, and strict separation of environments (dev/test/prod).
Encryption in transit using TLS 1.2+ and at rest using AES‑256 for platform storage and backups, including client-side encrypted off-site backups.
Strong access control with IAM, least-privilege roles, multi-level permissions, IP whitelisting, password policies, and support for SSO/SAML/OIDC integration.
Multi-tenant data isolation at the workspace/database level, plus workspace and user-level data filters to constrain row-level access.
Continuous monitoring, logging, vulnerability scanning of containers, and regular penetration testing, with 24/7 incident response procedures.
Compliance with major standards and regulations, including SOC 2 Type II, ISO 27001/27002, GDPR, CCPA, FERPA, GLBA, and optional HIPAA add-ons with BAAs.
GoodData releases updates frequently on a managed SaaS cadence, with changes rolled out centrally by GoodData rather than by customers.
Cloud release frequency: GoodData Cloud publishes regular “What’s New” updates and detailed release notes, showing feature and improvement releases multiple times per quarter, often monthly or more frequently.
Scheduled release windows: Individual cloud releases are scheduled maintenance events (for example, specific Thursdays at defined times), minimizing disruption while the platform is upgraded.
Continuous delivery model: As a SaaS product, GoodData Cloud is operated and maintained by GoodData; customers automatically receive new features, fixes, and security updates without manual patching.
Early Access/experimental features: New capabilities are first exposed as Early Access or experimental features that can be enabled per workspace, allowing teams to test them before broad adoption.
GoodData’s legal terms state that customers keep ownership of their data, while GoodData focuses on providing the platform and tools to store, process, and export that data. The specifics are governed by the signed agreement and product-specific terms for each deployment.
GoodData’s commercial contracts are subscription-based, with renewal and cancellation terms defined in the master agreement and product-specific terms rather than in a single public “policy” page. Public legal documents and license terms provide several useful data points you can use as a reference when negotiating.
Subscription model and term: GoodData subscriptions run for a defined term (for example, one year) under your order form or cloud terms; community and free editions explicitly use a one‑year term that automatically renews for additional one‑year periods unless either party gives advance notice of non‑renewal.
Automatic renewal: The GoodData.CN Community Edition license states that after the initial one‑year term, the agreement auto‑renews annually unless either party provides at least 30 days’ written notice of non‑renewal, which is a strong indicator of the pattern GoodData favors for time‑limited subscriptions.
Customer-initiated termination: In the free/platform terms, customers may terminate the agreement for convenience by providing written notice to GoodData (often 30 days), after which they can stop using the service; for enterprise cloud subscriptions, the exact notice period is set in the contract.
Termination for breach: Either party can terminate if the other materially breaches the agreement and fails to cure within 30 days of written notice, giving GoodData and the customer symmetrical “for cause” termination rights.
Vendor-initiated termination: GoodData may terminate with notice if continued use of the software could create IP or legal issues, and may suspend or discontinue services where necessary, as spelled out in the free and community license terms.
Effect of termination on access: On termination or expiration, all rights and licenses to use the platform cease and you must stop using the services; for self-hosted/community software, you must remove and destroy copies of the software from your systems.
Data retrieval after termination: Product-specific terms indicate that, upon termination of subscription services, GoodData will make customer data available for retrieval for a limited period (for example, 30 days) before deletion, which is important for exit planning and portability.
GoodData software meets several major security and privacy compliance standards that are commonly required by enterprises and regulated industries.
SOC 2 Type II: GoodData has maintained SOC 2 Type II certification since 2013, with regular independent audits covering Security, Availability, and Confidentiality.
ISO 27001 / ISO 27002: The platform’s Information Security Management System follows ISO 27001, and GoodData states that it implements all ISO 27001 Annex A controls and aligns practices with ISO 27002.
GDPR: GoodData affirms compliance with the EU and UK General Data Protection Regulation for processing personal data, including data processing agreements and SCCs where needed.
CCPA: The platform complies with the California Consumer Privacy Act, supporting data subject rights and related privacy obligations.
HIPAA: GoodData supports HIPAA for protected health information; HIPAA is available via a specific add-on/BAA rather than enabled by default in every deployment.
FERPA and GLBA: GoodData lists compliance with U.S. education (FERPA) and financial privacy (GLBA) regulations for relevant customer use cases.
GoodData
By GoodData Corporation
