Frequently Asked Questions

Yes. Bassirah proposes independent engineering services for Trino OSS, including distributed SQL architecture, connector configuration, security hardening, performance tuning, deployment automation and operational resilience planning. Scope and response commitments are defined in the engagement agreement.

Trino OSS services →

No. Independent Bassirah services do not imply official upstream support or foundation endorsement. Vendor-backed support applies only where separately covered by an appropriate commercial agreement.

Support hours and response commitments are contract-dependent and are documented in the statement of work and service-level agreement for each platform.

Nine: Trino, ClickHouse OSS, dbt Core / dbt OSS, DataHub Core, PostgreSQL, MongoDB Community Server, Apache Cassandra, Apache Superset and YugabyteDB. 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.

Open-Source Support overview →

No. Our independent services do not include vendor long-term support releases or vendor-issued security fixes. Within an agreed scope, we track the releases and security advisories that each project publishes, test upgrades and patches against your environment and apply them through an agreed change process. Where vendor-backed fixes and support are required, a commercial distribution or vendor agreement may be the better route.

Choose YugabyteDB when the workload needs what a distributed database provides: write volume or data size that one PostgreSQL primary cannot serve, writes that must continue through a node or zone failure without a manual failover step, or data that must be placed in, and served from, several regions through one SQL interface. Stay on PostgreSQL when one primary with read replicas, connection pooling and a tested failover meets your scale and recovery objectives, or when your users and data sit in one region: it is simpler to operate. YugabyteDB’s YSQL interface is PostgreSQL-compatible, but keys, query plans, latency between zones and some features and extensions behave differently, so we test your schema and workload before recommending a move.

YugabyteDB engineering → · PostgreSQL engineering →

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. Bassirah can help evaluate either route based on your security, connectors, operations and commercial requirements.

Compare the routes →

They represent two procurement and support routes into related technology: partner-led ClickHouse solutions and independent engineering services for the OSS edition. Architecture and available features depend on the selected deployment and entitlement.

Partner-led ClickHouse → · ClickHouse OSS →

The open-source dbt ecosystem has evolved. dbt v1 / dbt Core remains recognizable, while 2026 dbt v2 product naming uses dbt OSS for the Apache-licensed distribution. Bassirah names the exact version, adapter and distribution supported in every project.

dbt Core & dbt OSS services →

MongoDB Community Server is source-available under the Server Side Public License (SSPL) for modern releases. We include it under the broader “Open-Source & Community Support” website category rather than labeling it an OSI-approved open-source product.

ClickHouse, Starburst, Redis, Langfuse, MinIO AIStor, MongoDB, Postman and Strategy. Partner solutions are delivered within each vendor’s commercial program, where licensed capabilities and vendor-backed support may apply. Our partner portfolio and our independent open-source practice are complementary but commercially distinct.

Strategic Partners →

Trino provides connectors and S3-compatible storage integration for suitable lakehouse patterns, including Apache Iceberg. The exact AIStor product configuration, catalog, network and connector compatibility must be validated in the target architecture.

Open Iceberg Lakehouse blueprint →

DataHub Core provides metadata discovery, lineage and governance workflows, but actual data authorization is generally enforced in the connected query engines, databases and security systems. Designs must define which system is the policy decision point and which is the enforcement point.

Yes, as an engineering offering subject to the platform’s technical limits and agreed requirements. Trino query retry, coordinator recovery, stateful services, object storage, networking and dependent catalogs must be addressed separately, with customer-approved RTO and RPO and tested procedures.

Platform Reliability →

On-premises, private cloud and hybrid environments, where the selected technologies support them. Customer-controlled or isolated deployment patterns are designed and validated per engagement.

No. Trino (or Starburst) federates SQL queries across many existing sources, while ClickHouse is a purpose-built analytical database for low-latency serving of data stored in it. Many architectures use both, each for its own role. We choose based on workload, latency, data location and operating model.

Architecture Blueprints →

A discovery or architecture assessment usually defines business objectives, current stack, volumes, performance, security, support needs, constraints and success metrics. Bassirah can then propose an implementation plan or focused proof of concept.

Workshop formats →

Yes, through managed services with defined accountability. Scope can range from scheduled health reviews and upgrade planning to contracted monitoring, incident, problem and change procedures and backup and restore testing. Service windows and response terms are agreed in the contract for each platform.

Managed Services →

Yes. Our Migration & Modernization service plans and executes moves with traceability and controlled risk, for example from proprietary relational databases to PostgreSQL, or offloading suitable warehouse workloads to an open lakehouse where the source and query economics justify it. Each migration starts with an assessment and agreed acceptance criteria.

Migration & Modernization →

Please don’t. Use the form to describe your objective and context only. After the first conversation, we agree a secure channel for architecture diagrams, sample data or any other sensitive material. Never send credentials.