Frequently Asked Questions

Clixer is a Decision Intelligence platform that processes data in real time and supports decisions with AI. Classic BI tools show 'what happened'; Clixer answers 'why it happened' and takes action with your approval.

BI visualises data and leaves interpretation to you. Decision Intelligence goes beyond visualisation: it catches deviations automatically, explains root causes, suggests what to do and applies the action through an approval mechanism. Clixer delivers both layers in one platform.

Three core differences: (1) ETL, the analytics engine, data reconciliation and AI in one platform, no extra tools or separate licences. (2) Company-based, predictable licensing instead of per-user dollar-based seats. (3) It continues where BI stops: catches anomalies, explains causes, takes approved action.

Clixer is as much a complement to Power BI as a competitor. Without disrupting your current reporting you can add the decision layer (anomaly detection, root cause, forecasting, approved actions) with Clixer, and migrate reporting over time. Most of our customers transition gradually.

We have live deployments across multi-branch retail and F&B chains, universities, holdings, healthcare, maritime and fintech. Multi-location scenarios, branch benchmarking, LFL, target tracking, are where we are strongest.

Yes. Clixer is 100% developed in Türkiye. That means local-currency pricing, Turkish-first AI, a local support team and your data staying in-country.

No. Cockpits are designed with drag-and-drop and questions are asked in natural language. The AI assistant builds the query, draws the chart and comments on it. Your IT team is only involved in the initial data connection.

Unlimited. Licensing is company-based, so whether you add 10 users or 500, your cost doesn't change. Wide adoption is encouraged in our model, not penalised.

Yes. Leave a request through the contact form and we'll schedule a 30-minute live demo with a scenario similar to your data structure. We also offer a measurable, short-term PoC programme.

It connects directly to MSSQL, PostgreSQL, MySQL and Oracle databases, and you can import Excel files. Whatever the connection type, data is unified on one platform. If you need another source, we add it to our connector roadmap.

No. ETL is built into Clixer. Extraction, transformation and scheduled synchronisation are part of the platform, managed from the UI, without writing code.

If your ERP runs on one of the databases above (most enterprise ERPs do), it connects directly. We have live deployments pulling data from systems such as Logo, Netsis and SAP.

Within minutes, depending on the sync strategy. Seven smart synchronisation strategies (incremental, date-based, gap repair and more) apply the most efficient method for your data volume.

No. Clixer copies data into its own analytics engine; dashboards never query your source database directly. The reporting load sits entirely on Clixer, and synchronisation runs incrementally so the source is never strained.

Yes. Upload an Excel file from the UI, create a dataset in minutes and build a cockpit on top. It's an ideal start for teams that want to begin small and move to database connections later.

Yes. Sales data can live in MSSQL and HR data in PostgreSQL; both sync into Clixer and are analysed side by side in the same cockpit.

Clixer's reconciliation agent automatically detects and reports differences between your source system and the analytics warehouse (missing days, duplicate records and more). This is a capability competing platforms don't offer.

The agent pinpoints the difference at day/month precision, asks for your approval and repairs the data from the source after approval. Everything is recorded in the audit log, nothing changes silently.

It runs automatically on schedule (e.g. every night) and can be triggered manually anytime. The result report is emailed to stakeholders.

It was designed exactly for this. Records changed retroactively at the source (returns, correction invoices, late entries) are caught in the reconciliation scan and the affected period is re-synchronised. Your reports never fall behind the source.

Clixer uses a columnar engine designed for analytics (ClickHouse) plus smart caching. Sub-second query response on datasets of millions of rows is proven in live customer deployments. As data grows, the architecture scales horizontally.

No. The read layer works through the cache; response times hold even when every manager opens the same cockpit on Monday morning.

Classic BI tools query general-purpose databases or try to squeeze data into memory. Clixer uses a columnar OLAP engine built for analytical queries plus a Redis cache layer. The architectural difference is felt as a waiting-time difference.

Our live deployments work with tables of hundreds of millions of rows. The ClickHouse architecture scales to billions; the limit is the hardware you choose, not the software.

You ask questions in natural language ('What's the LFL change vs last month?', 'Why did we drop yesterday?'); the assistant builds the query, draws the chart and comments. Anomaly detection, root-cause analysis, sales forecasting and what-if simulation are also part of the AI layer.

No. Clixer AI is not a general chatbot; it is bound to your data schema. The SQL behind every answer is transparent and passes a deterministic validator. When unsure, it asks a question instead of inventing an answer.

Every AI answer has a 'show SQL' option. You can see which table, which filter and which calculation produced the result. There is no black box; transparency is a design principle.

No. Your data is processed only to serve you; it is never used to train any model.

Eight rule types catch deviations per branch and metric: below-budget, day-over-day drops, negative divergence from peer stores and more. It sends proactive notifications with root-cause analysis, it tells you before you ask.

Yes. Through the corporate knowledge base (RAG) you can teach company-specific definitions: rules like 'Performance = visitor count' or 'mall stores are closed on Sundays' are reflected in AI answers.

Models combining regression, EWMA and confidence bands project forward from historical data. You can track forecast-vs-actual fit and get alerts when the gap grows.

It lets you compare scenarios side by side by changing parameters ('what if prices rise 5%', 'what if visitors drop 10%'). You rehearse the decision before you make it.

Yes, natively. It makes fair period-over-period comparisons with a comparable store/branch set, isolating the effect of newly opened or closed locations. It's one of the most used modules among retail and F&B chains.

No. Cockpits are designed with drag-and-drop. KPI cards, trend charts, ranking lists, heat maps, funnels, maps and more come as ready components.

Yes. With the Unified Metric Engine you derive new metrics from existing ones without code (e.g. Returns/Revenue×100). A defined metric behaves identically across cockpits, mobile and AI answers, one definition, consistent everywhere.

No. With row-level security (RLS), each user sees only the branch/region/category they are entitled to. The regional manager sees their region, the CEO sees everything, in the same cockpit, without separate reports.

Yes. With subscriptions, a snapshot of the cockpit you choose is sent automatically to the people and time you set. Management finds the up-to-date picture in their inbox every morning.

Yes. Click from a summary KPI into the store breakdown, then into day and product detail. The answer to 'why is this number what it is' is two clicks away.

Yes. Logo, colours and labels (e.g. 'branch', 'dealer' or 'campus' instead of 'store') are fully customisable. The platform speaks your language.

Yes. With its PWA architecture it is fully functional on phones and tablets. Field teams, regional managers and executives access cockpits from anywhere.

Yes. In offline mode you keep working with the last synced data; when connectivity returns, delta sync updates only what changed. Your data is with you in a warehouse, a mall basement or on a plane.

No; add it to your home screen from the browser for an app experience. If preferred corporately, native packaging (iOS/Android) is also available.

Your choice: entirely on your own servers (on-premise) or in an isolated cloud environment dedicated to you. In both models your data is never shared with third parties and never leaves the country.

Mandatory two-factor authentication (2FA), row-level security (RLS), AES-encrypted connection credentials, rate limiting, SSRF protection, JWT rotation and a full audit trail. The platform has been penetration-tested for externally exposed enterprise deployments.

Data locality (the on-premise option), role-based access control, the audit trail and the encryption architecture are designed to support your KVKK/GDPR obligations.

Yes. The audit log records critical operations at who/when/what level. It is ready for the audit requirements of regulated industries.

Yes. User synchronisation with your existing corporate directory is supported; you never manage your users twice.

It is company-based, not per-user. However many users you add, your licence cost does not change. Local-currency pricing removes exchange-rate risk.

In per-user dollar models every new user is a cost, so companies restrict access and data culture never spreads. With a company licence it's the opposite: the more people use it, the more the investment pays off.

In classic BI the licence is only the beginning: add an ETL tool, a data warehouse, consulting and analyst headcount. In Clixer, ETL, the analytics engine, AI and reconciliation are one package. Compare total cost, not licence price, on request we prepare a company-specific TCO analysis.

You start with the core platform (connections, ETL, cockpits, reporting) and add modules like the AI assistant, anomaly/forecasting and the reconciliation agent as needed. Starting small and growing is possible.

Standard installation and the first data connection typically take days; compared with classic BI projects that take weeks, you see your first cockpit much sooner.

Only access to the data source (a read-only user) and the server/environment for installation. The rest, setup, connection, first cockpit and training, is handled by the Clixer team.

We deliver role-based training during onboarding (admin, designer, end user). The in-platform Training Centre also keeps step-by-step guides and scenario walkthroughs at hand.

In Turkish, with a local team. The maintenance agreement covers version updates, health monitoring and priority support. You never wait in a foreign vendor's ticket queue.

Updates are applied in a maintenance window with minutes of downtime and are rollback-safe. In on-premise deployments you set the update schedule.

Yes. Thanks to the white-label architecture you can sell Clixer under your own brand. We offer a revenue-sharing partner model for ERP dealers, software houses and integrators.

The end-to-end look including brand name, logo, colours and domain. Your customer experiences the platform as your product.

Yes. The interface ships in Turkish and English, and the multilingual infrastructure extends to new languages. International deployments through our white-label partners are a target market.