OPEN-SOURCE & COMMUNITY ENGINEERING
Open Technologies. Production-Grade Engineering.
Modern enterprises rely on community technologies for flexibility, innovation and control. Bassirah helps teams deploy and operate these platforms safely, with architecture reviews, security design, high availability, migration support, tuning, knowledge transfer and optional managed services.
Nine platforms · Four practice areas · Independent engineering, transparently scoped
Independent engineering, clearly scoped.
These are independent Bassirah engineering and support offerings. They do not imply upstream vendor or foundation endorsement, official vendor support rights, enterprise feature entitlement or maintenance guarantees.
Project and product names are trademarks of their respective owners. MongoDB Community Server is source-available under the SSPL, not OSI-approved open source.
THE OPERATING REALITY
The Software Is Free to Adopt. Running It Well Is an Engineering Discipline.
Open-source and community platforms give enterprises control over deployment topology, infrastructure choice, data location and upgrade timing. That control also moves responsibility in-house: sizing, security hardening, high availability, backup and restore, upgrades and incident response all belong to the team operating the platform.
Bassirah fills that gap with independent engineering. We design the architecture, implement it on your infrastructure, prove that recovery works, and either hand operations over to your team with documented runbooks or operate the platform with you under an agreed support scope.
- Architecture decisions recorded before anything is deployed
- Security, identity and network controls designed in, not added later
- Recovery procedures tested, not just documented
- Upgrade paths validated against your workloads and integrations
- Knowledge transfer built into every engagement
THE PORTFOLIO
Nine Platforms. Four Practice Areas.
We group the portfolio by the job each technology does in your data estate, so the right specialists engage from the first conversation.
| Category | Technologies | Typical engagement |
|---|---|---|
| Distributed SQL & analytical engines | Trino OSS; ClickHouse OSS | Federation, cluster design, analytics performance, security and HA/DR |
| Transformation & governance | dbt Core / dbt OSS; DataHub Core | Modeling, lineage, metadata ingestion, CI/CD and governance |
| Operational databases | PostgreSQL; MongoDB Community; Apache Cassandra; YugabyteDB | Operational DBA/SRE, data architecture, scaling and resilience |
| Business intelligence & visualization | Apache Superset | Dashboards, semantic datasets, security, caching and embedded analytics |
Query Engines
Trino OSS
Federated SQL across lakes, warehouses and supported operational databases, without unnecessary data movement.
ClickHouse OSS
Self-managed, column-oriented analytics for high-volume events, telemetry and analytical APIs.
Analytics Engineering & Governance
dbt Core & dbt OSS
Modular, tested and documented SQL transformations with CI/CD discipline.
DataHub Core
Metadata catalog, ownership, glossary and lineage for a discoverable data estate.
Databases
PostgreSQL
Extensible relational foundation, engineered for replication, recoverability and tuned performance.
MongoDB Community
Document database engineering with clear licensing, security and operational guardrails.
Apache Cassandra
Partition-aware, multi-datacenter distributed data with disciplined repair and capacity operations.
YugabyteDB
Distributed SQL with PostgreSQL-compatible YSQL, engineered for multi-zone resilience and scale-out growth.
BI & Visualization
Apache Superset
Governed dashboards and self-service exploration on your lakehouse and databases, with secure, scalable deployment.
TRANSPARENT CHOICES
Three Technologies Appear in Both Portfolios. Here Is Why.
Trino and ClickHouse are available to you through a community route supported independently by Bassirah, or through a partner-led commercial route. They are different propositions with different assurances, so they have separate pages. We help you choose based on capability, support and commercial requirements, not on habit.
Trino OSS or Starburst Enterprise
Trino is the open-source distributed SQL engine. Starburst Enterprise is a commercial distribution based on Trino, with additional product capabilities and vendor support options under contract.
ClickHouse OSS or Partner-Led ClickHouse
Run community ClickHouse yourself with independent Bassirah engineering, or engage partner-led ClickHouse offerings where commercial entitlements and vendor-backed support matter.
MongoDB Community or Partner-Led MongoDB
Run MongoDB Community Server (source-available, SSPL) yourself with independent Bassirah engineering, or engage partner-led MongoDB Atlas or Enterprise Advanced where commercial capabilities and vendor-backed support matter.
We never present a community edition as if it included commercial features, and we never present a commercial product as a requirement where the community edition meets your objectives.
ENGINEERING SCOPE
From First Design Review to Ongoing Operations
Each platform page lists platform-specific deliverables. Across all nine, engagements draw from the same engineering scope.
- Architecture reviews — workload fit, topology, sizing assumptions and documented decisions.
- Security design — TLS, authentication, authorization, secrets handling and network controls.
- High availability — replication, failover and recovery patterns appropriate to each technology.
- Backup and disaster recovery — tested restore procedures against customer-approved RTO and RPO.
- Migration support — compatibility assessment, cutover planning, reconciliation and rollback points.
- Performance tuning — query, schema, memory and concurrency improvements based on measured workload evidence.
- Upgrade and lifecycle management — release evaluation, compatibility testing and controlled rollout.
- Knowledge transfer and optional managed services — runbooks, handover sessions, and contracted operations where you want them.
ENGAGEMENT MODELS
Choose the Level of Engagement That Fits Your Operating Model
Start with focused advisory work, add scheduled platform care, or engage Bassirah for contracted operations. Standard response targets are published in our support model; scope and coverage are confirmed in each statement of work.
Packages describe independent Bassirah engineering. They do not include upstream vendor support, vendor security fixes, long-term-support releases or licensed enterprise features. Standard initial response targets are published in our support model; restoration times are never guaranteed.
HOW WE WORK
A Predictable Path From Assessment to Accountable Operations
- AssessReview workloads, current topology, versions, integrations, security posture and operating pain points. Output: findings and a prioritized risk register.
- DesignAgree target architecture, sizing assumptions, security model and recovery objectives. Output: architecture decision records and reference design.
- ImplementDeploy or remediate using infrastructure-as-code where appropriate, with configuration under version control. Output: working environment and test evidence.
- ProveRun performance, failover and restore tests against agreed acceptance criteria. Output: validation report.
- Operate or hand overTransfer runbooks and knowledge to your team (hand over), or continue under a contracted support package. Output: runbooks, RACI and operating cadence.
Already running one of these platforms?
Start with a health check of your current deployment.
LICENSING
Know What Each License Means Before You Standardize
Licensing affects how you deploy, distribute and offer software as a service. We record the license of the exact release you run as part of every assessment. This summary is for orientation only and is not legal advice.
| Platform | License (community edition) | Classification on this site |
|---|---|---|
| Trino | Apache License 2.0 | Open source |
| ClickHouse OSS | Apache License 2.0 | Open source |
| dbt Core / dbt OSS | Apache License 2.0 for the openly licensed distributions | Open source (confirm per component) |
| DataHub Core | Apache License 2.0 | Open source |
| PostgreSQL | PostgreSQL License | Open source |
| MongoDB Community Server | Server Side Public License (SSPL) for releases since October 2018 | Source-available, not OSI-approved open source |
| Apache Cassandra | Apache License 2.0 | Open source |
| Apache Superset | Apache License 2.0 | Open source |
| YugabyteDB | Apache License 2.0 (core database) | Open source (commercial YugabyteDB Anywhere and Aeon are separate products) |
Open-Source Support: Frequently Asked Questions
Is Bassirah an official vendor or foundation partner for these projects?
No. Our open-source and community offerings are independent engineering and support services. They do not imply endorsement by project maintainers, foundations or vendors, and they do not include official vendor support rights. Vendor-backed support applies only where separately covered by an appropriate commercial agreement.
Do your support services include security patches or long-term-support releases?
We do not produce vendor security fixes or vendor LTS releases. We monitor upstream advisories and releases relevant to your versions, assess their impact, test upgrades against your workloads and plan controlled rollouts. The scope of that work is defined in your statement of work.
What support coverage does Bassirah offer for open-source platforms?
Coverage for a specific open-source platform depends on the contract. Support windows, severity definitions and response terms are documented in the statement of work and service-level agreement for each engagement. Our open-source support model explains how severity, response and upstream responsibilities work.
Is MongoDB Community open source?
MongoDB Community Server is source-available under the Server Side Public License for modern releases. We include it under the broader “Open-Source & Community Support” category rather than labeling it as OSI-approved open source.
Can you support a platform we already run in production?
Yes. Most engagements start with a health assessment of the existing deployment: versions, topology, configuration, security, backup and recovery, and observability. The findings define a remediation plan and, if you want it, an ongoing support scope.
What if we later need a commercial edition?
We help you evaluate when commercial capabilities or vendor assurances justify a change, for example Starburst Enterprise for Trino workloads or partner-led ClickHouse offerings. Where a phased coexistence or migration is the right answer, we plan it with you.
Run Open Technology With Confidence.
Tell us which platforms you run or plan to adopt, and what keeps your team up at night. We will propose an assessment scope and a practical next step.