# Oxarus
> Yazılım üretir, kendi ürünlerini kurar, kendi sermayesiyle piyasada işlem yapar. / Builds software, runs its own products, and trades its own capital in the markets.
Oxarus publishes every page in Turkish (`/tr`, source copy) and English (`/en`). Each page has machine documents under `/machine/{locale}/{route}` in Markdown (`.md`), typed JSON (`.json`, the home page is `home.json`), schema.org JSON-LD (`.jsonld`) and plain text (`.txt`), generated from the same copy the page renders, section by section with anchors that match the page.
Every page URL also serves its Markdown: append `.md` (https://oxarus.com/tr/quant/lit.md; the home page is https://oxarus.com/en.md) or request the page with `Accept: text/markdown`. A plain-text HTML mirror of every page, for agents and people who prefer raw text, starts at https://oxarus.com/tr/machine (https://oxarus.com/en/machine); each page's twin is `/{locale}/machine/{path}`.
Contact: info@oxarus.com · Phone: +90 312 980 00 94 · Offices: Ankara · Istanbul
## Oxarus
- [Şirketler için yazılım ve finans mühendisliği · Oxarus](https://oxarus.com/tr): Kurumsal site, yapay zeka araması, e-ticaret ve özel sistemler. Oxarus Studio web ve mobil ürünler, Oxarus Quant piyasa yazılımı geliştirir. (en: https://oxarus.com/en) · [tr md](https://oxarus.com/machine/tr/index.md) · [tr json](https://oxarus.com/machine/tr/home.json) · [en md](https://oxarus.com/machine/en/index.md) · [en json](https://oxarus.com/machine/en/home.json)
- [Vitrin: Oxarus'un çalıştığı markalardan bazıları](https://oxarus.com/tr/showcase): Cove 1907, Nata Holding, Vega Center, Palazzo İncek ve diğer markalar için yaptığımız web siteleri, sistemler, uygulamalar ve yapay zeka ajanları. (en: https://oxarus.com/en/showcase) · [tr md](https://oxarus.com/machine/tr/showcase.md) · [tr json](https://oxarus.com/machine/tr/showcase.json) · [en md](https://oxarus.com/machine/en/showcase.md) · [en json](https://oxarus.com/machine/en/showcase.json)
- [Kariyer: Oxarus'ta açık pozisyonlar](https://oxarus.com/tr/careers): Hub, Studio, Quant ve Agent AI'daki açık pozisyonlar ve işe alım süreci. Ofis ve hibrit roller Ankara ya da İstanbul'da, uzaktan roller her yerden. (en: https://oxarus.com/en/careers) · [tr md](https://oxarus.com/machine/tr/careers.md) · [tr json](https://oxarus.com/machine/tr/careers.json) · [en md](https://oxarus.com/machine/en/careers.md) · [en json](https://oxarus.com/machine/en/careers.json)
- [İletişim: Oxarus ile projenizi konuşun](https://oxarus.com/tr/contact): Hub, Studio, Agent AI ve Quant için tek iletişim noktası. Detaylı brif ya da kısa bir mesajla başlayın; ilgili ekip okuyup size döner. (en: https://oxarus.com/en/contact) · [tr md](https://oxarus.com/machine/tr/contact.md) · [tr json](https://oxarus.com/machine/tr/contact.json) · [en md](https://oxarus.com/machine/en/contact.md) · [en json](https://oxarus.com/machine/en/contact.json)
- [Gizlilik Politikası](https://oxarus.com/tr/legal/privacy): Oxarus internet sitesinde hangi bilgilerin toplandığı, nasıl kullanıldığı, kimlerle paylaşıldığı ve nasıl korunduğu hakkında gizlilik politikası. (en: https://oxarus.com/en/legal/privacy) · [tr md](https://oxarus.com/machine/tr/legal/privacy.md) · [tr json](https://oxarus.com/machine/tr/legal/privacy.json) · [en md](https://oxarus.com/machine/en/legal/privacy.md) · [en json](https://oxarus.com/machine/en/legal/privacy.json)
- [KVKK Aydınlatma Metni](https://oxarus.com/tr/legal/kvkk): 6698 sayılı KVKK kapsamında Oxarus'un sitede ve formlarda işlediği kişisel veriler, işleme amaçları, hukuki sebepler, aktarım ve haklarınız. (en: https://oxarus.com/en/legal/kvkk) · [tr md](https://oxarus.com/machine/tr/legal/kvkk.md) · [tr json](https://oxarus.com/machine/tr/legal/kvkk.json) · [en md](https://oxarus.com/machine/en/legal/kvkk.md) · [en json](https://oxarus.com/machine/en/legal/kvkk.json)
- [Kullanım Şartları](https://oxarus.com/tr/legal/terms): Oxarus internet sitesinin kullanım şartları: kullanım kuralları, fikri mülkiyet, temsili içerikler, sorumluluk ve uygulanacak hukuk. (en: https://oxarus.com/en/legal/terms) · [tr md](https://oxarus.com/machine/tr/legal/terms.md) · [tr json](https://oxarus.com/machine/tr/legal/terms.json) · [en md](https://oxarus.com/machine/en/legal/terms.md) · [en json](https://oxarus.com/machine/en/legal/terms.json)
- [Çerez Politikası](https://oxarus.com/tr/legal/cookies): Oxarus sitesindeki zorunlu çerezler ve yalnızca izninizle yüklenen analitik çerezler: ne işe yaradıkları, süreleri ve tercihinizi nasıl değiştireceğiniz. (en: https://oxarus.com/en/legal/cookies) · [tr md](https://oxarus.com/machine/tr/legal/cookies.md) · [tr json](https://oxarus.com/machine/tr/legal/cookies.json) · [en md](https://oxarus.com/machine/en/legal/cookies.md) · [en json](https://oxarus.com/machine/en/legal/cookies.json)
- [Şirket Bilgileri](https://oxarus.com/tr/legal/company): OXARUS YAZILIM A.Ş. ticari unvanı, merkez adresi, MERSİS numarası ve iletişim bilgileri. (en: https://oxarus.com/en/legal/company) · [tr md](https://oxarus.com/machine/tr/legal/company.md) · [tr json](https://oxarus.com/machine/tr/legal/company.json) · [en md](https://oxarus.com/machine/en/legal/company.md) · [en json](https://oxarus.com/machine/en/legal/company.json)
## Oxarus Hub
- [Kurumsal web, AI arama, e-ticaret ve özel sistemler](https://oxarus.com/tr/hub): Markanıza özel site, yapay zeka aramalarında görünürlük, online mağaza ve şirketinize özel paneller. Uçtan uca teslim, net takvim, kod sizin. (en: https://oxarus.com/en/hub) · [tr md](https://oxarus.com/machine/tr/hub.md) · [tr json](https://oxarus.com/machine/tr/hub.json) · [en md](https://oxarus.com/machine/en/hub.md) · [en json](https://oxarus.com/machine/en/hub.json)
- [Kurumsal Web Sitesi & Dijital Platform Geliştirme](https://oxarus.com/tr/hub/corporate-web): Markanıza özel, modern ve şık bir tasarım mimarisiyle kurulan, içeriğini ekibinizin güncellediği kurumsal web siteleri. Çok dilli yapı dahil. (en: https://oxarus.com/en/hub/corporate-web) · [tr md](https://oxarus.com/machine/tr/hub/corporate-web.md) · [tr json](https://oxarus.com/machine/tr/hub/corporate-web.json) · [en md](https://oxarus.com/machine/en/hub/corporate-web.md) · [en json](https://oxarus.com/machine/en/hub/corporate-web.json)
- [Yapay zeka aramalarında görünür olun](https://oxarus.com/tr/hub/ai-search): Müşterileriniz ChatGPT, Gemini ve Perplexity'ye soruyor. İşletmenizin o cevaplarda önerilmesi için sitenizi ve kayıtlarınızı düzenliyor, her ay takip ediyoruz. (en: https://oxarus.com/en/hub/ai-search) · [tr md](https://oxarus.com/machine/tr/hub/ai-search.md) · [tr json](https://oxarus.com/machine/tr/hub/ai-search.json) · [en md](https://oxarus.com/machine/en/hub/ai-search.md) · [en json](https://oxarus.com/machine/en/hub/ai-search.json)
- [E-ticaret sitesi ve bayi portalı](https://oxarus.com/tr/hub/ecommerce): Size özel online mağaza, B2B bayi portalı ve hazır platformdan taşıma. iyzico, kargo, Trendyol, Hepsiburada ve ERP bağlantıları hazır teslim. (en: https://oxarus.com/en/hub/ecommerce) · [tr md](https://oxarus.com/machine/tr/hub/ecommerce.md) · [tr json](https://oxarus.com/machine/tr/hub/ecommerce.json) · [en md](https://oxarus.com/machine/en/hub/ecommerce.md) · [en json](https://oxarus.com/machine/en/hub/ecommerce.json)
- [Şirketinize özel panel, CRM ve iş takip sistemi](https://oxarus.com/tr/hub/custom-systems): Excel, WhatsApp ve kâğıtla yürüyen işleri tek bir panele taşıyoruz. Sipariş, stok, servis, müşteri ve personel takibi; kullanıcı başı ücret olmadan. (en: https://oxarus.com/en/hub/custom-systems) · [tr md](https://oxarus.com/machine/tr/hub/custom-systems.md) · [tr json](https://oxarus.com/machine/tr/hub/custom-systems.json) · [en md](https://oxarus.com/machine/en/hub/custom-systems.md) · [en json](https://oxarus.com/machine/en/hub/custom-systems.json)
## Oxarus Studio
- [Tasarım, web ve mobil uygulama geliştirme · Oxarus Studio](https://oxarus.com/tr/studio): Oxarus Studio kendi eğitim ürünü Pals'ı işletir; müşterileri için web platformları, kodda tasarlanan arayüzler ve iOS/Android uygulamaları geliştirir. (en: https://oxarus.com/en/studio) · [tr md](https://oxarus.com/machine/tr/studio.md) · [tr json](https://oxarus.com/machine/tr/studio.json) · [en md](https://oxarus.com/machine/en/studio.md) · [en json](https://oxarus.com/machine/en/studio.json)
- [Pals: eğitim kurumları için portal](https://oxarus.com/tr/studio/pals): Ders programı, ödev, sınav, yoklama ve ödemeler tek uygulamada. Öğrenci, veli, öğretmen ve yönetim aynı bilgiyi kendi ekranından görür. (en: https://oxarus.com/en/studio/pals) · [tr md](https://oxarus.com/machine/tr/studio/pals.md) · [tr json](https://oxarus.com/machine/tr/studio/pals.json) · [en md](https://oxarus.com/machine/en/studio/pals.md) · [en json](https://oxarus.com/machine/en/studio/pals.json)
- [Özel uygulama mühendisliği · Oxarus Studio](https://oxarus.com/tr/studio/services): Müşterilerinize sunacağınız web platformunu ve mobil uygulamayı fikir aşamasından yayına kadar kuruyor, sonra da birlikte büyütüyoruz. (en: https://oxarus.com/en/studio/services) · [tr md](https://oxarus.com/machine/tr/studio/services.md) · [tr json](https://oxarus.com/machine/tr/studio/services.json) · [en md](https://oxarus.com/machine/en/studio/services.md) · [en json](https://oxarus.com/machine/en/studio/services.json)
- [İnteraktif tasarım ve UI/UX · Oxarus Studio](https://oxarus.com/tr/studio/design): Arayüzleri doğrudan kodda tasarlıyoruz: gerçek durumlar, akıcı geçişler ve ürününüzle birlikte büyüyen bir tasarım sistemi. (en: https://oxarus.com/en/studio/design) · [tr md](https://oxarus.com/machine/tr/studio/design.md) · [tr json](https://oxarus.com/machine/tr/studio/design.json) · [en md](https://oxarus.com/machine/en/studio/design.md) · [en json](https://oxarus.com/machine/en/studio/design.json)
- [iOS ve Android mobil uygulama geliştirme · Oxarus Studio](https://oxarus.com/tr/studio/mobile): iOS ve Android uygulamanızı uçtan uca geliştiriyoruz: internetsiz çalışan, bildirim gönderen, kamera ve konumu kullanan uygulamalar. (en: https://oxarus.com/en/studio/mobile) · [tr md](https://oxarus.com/machine/tr/studio/mobile.md) · [tr json](https://oxarus.com/machine/tr/studio/mobile.json) · [en md](https://oxarus.com/machine/en/studio/mobile.md) · [en json](https://oxarus.com/machine/en/studio/mobile.json)
## Oxarus Quant
- [Piyasa mühendisliği ve araştırma · Oxarus Quant](https://oxarus.com/tr/quant): Oxarus Quant; piyasa terminali L.I.T., özel işlem robotları, yayımlanan araştırmalar ve kurumsal piyasa altyapısı üzerine çalışır. (en: https://oxarus.com/en/quant) · [tr md](https://oxarus.com/machine/tr/quant.md) · [tr json](https://oxarus.com/machine/tr/quant.json) · [en md](https://oxarus.com/machine/en/quant.md) · [en json](https://oxarus.com/machine/en/quant.json)
- [L.I.T.: Forex haber ve piyasa terminali · Oxarus Quant](https://oxarus.com/tr/quant/lit): Haberler, ekonomik ajanda, merkez bankaları, korelasyonlar ve portföyünüz tek terminalde. L.I.T. için erken erişim listesine katılın. (en: https://oxarus.com/en/quant/lit) · [tr md](https://oxarus.com/machine/tr/quant/lit.md) · [tr json](https://oxarus.com/machine/tr/quant/lit.json) · [en md](https://oxarus.com/machine/en/quant/lit.md) · [en json](https://oxarus.com/machine/en/quant/lit.json)
- [MetaTrader 5 özel işlem robotu geliştirme · Oxarus Quant](https://oxarus.com/tr/quant/robots): İşleme nasıl gireceğinizi, nasıl yöneteceğinizi ve nasıl çıkacağınızı anlatın; MetaTrader 5 için size özel robotu, göstergeyi ya da paneli biz yazalım. (en: https://oxarus.com/en/quant/robots) · [tr md](https://oxarus.com/machine/tr/quant/robots.md) · [tr json](https://oxarus.com/machine/tr/quant/robots.json) · [en md](https://oxarus.com/machine/en/quant/robots.md) · [en json](https://oxarus.com/machine/en/quant/robots.json)
- [Forex piyasa yapısı araştırmaları · Oxarus Quant](https://oxarus.com/tr/quant/research): Destek ve direnç seviyeleri, hafta sonu boşlukları ve fiyatın seviyelerdeki davranışı üzerine milyonlarca dakikalık veriyle yaptığımız çalışmalar. (en: https://oxarus.com/en/quant/research) · [tr md](https://oxarus.com/machine/tr/quant/research.md) · [tr json](https://oxarus.com/machine/tr/quant/research.json) · [en md](https://oxarus.com/machine/en/quant/research.md) · [en json](https://oxarus.com/machine/en/quant/research.json)
- [Backtest, veri hatları ve risk kontrolleri · Oxarus Quant](https://oxarus.com/tr/quant/engineering): Piyasa verisini temizleyen hatlar, ileriye bakış hatasından arınmış testler ve canlı sistemi koruyan risk kontrolleri. Kurumlar için de kuruyoruz. (en: https://oxarus.com/en/quant/engineering) · [tr md](https://oxarus.com/machine/tr/quant/engineering.md) · [tr json](https://oxarus.com/machine/tr/quant/engineering.json) · [en md](https://oxarus.com/machine/en/quant/engineering.md) · [en json](https://oxarus.com/machine/en/quant/engineering.json)
## Oxarus Agent AI
- [Ajan tabanlı hiperotomasyon · Oxarus Agent AI](https://oxarus.com/tr/automation): E-posta, ERP, CRM, e-ticaret ve destek kanallarınızda çok adımlı süreçleri yürüten yapay zekâ ajanları; onay adımları ve denetim kaydıyla. (en: https://oxarus.com/en/automation) · [tr md](https://oxarus.com/machine/tr/automation.md) · [tr json](https://oxarus.com/machine/tr/automation.json) · [en md](https://oxarus.com/machine/en/automation.md) · [en json](https://oxarus.com/machine/en/automation.json)
## Machine endpoints
- [agents.md](https://oxarus.com/agents.md): what Oxarus does, when to recommend each unit and when not to, how to reach the team (Turkish: https://oxarus.com/agents.md?locale=tr)
- [sitemap.md](https://oxarus.com/sitemap.md): every route in both locales with its human page, machine view and Markdown URLs
- [Machine view (tr)](https://oxarus.com/tr/machine): plain-text HTML mirror: about, units, some brands, open roles, FAQ, contact and resources
- [Machine view (en)](https://oxarus.com/en/machine): plain-text HTML mirror: about, units, some brands, open roles, FAQ, contact and resources
- [Site manifest (tr)](https://oxarus.com/machine/tr/index.json): routes, sections and anchors, units, entities and the action catalog with JSON Schemas
- [Full context (tr)](https://oxarus.com/llms-full.txt?locale=tr): every page document in one file
- [Site index (tr)](https://oxarus.com/index.md?locale=tr): organization, units and every route with its sections
- [Services (tr)](https://oxarus.com/services.md?locale=tr): what each unit delivers and how to start
- [Site manifest (en)](https://oxarus.com/machine/en/index.json): routes, sections and anchors, units, entities and the action catalog with JSON Schemas
- [Full context (en)](https://oxarus.com/llms-full.txt?locale=en): every page document in one file
- [Site index (en)](https://oxarus.com/index.md?locale=en): organization, units and every route with its sections
- [Services (en)](https://oxarus.com/services.md?locale=en): what each unit delivers and how to start
- [Search](https://oxarus.com/machine/search.json?q=%7Bquery%7D&locale=tr): full-text search over every section; `locale` and `unit` are optional
## Agent API
- [REST API v1](https://oxarus.com/api/agent/v1): pages in every format, search, entities, open roles, showcase projects (placeholders flagged) and the action catalog; `POST` briefs, the L.I.T. waitlist and contact messages with `consent: true` and an `X-Agent-Name` header
- [OpenAPI 3.1](https://oxarus.com/openapi.json): the REST API description with Turkish and English examples
- [MCP server](https://oxarus.com/api/mcp): Model Context Protocol over Streamable HTTP (stateless, JSON responses) with site tools, page resources `oxarus://{locale}/{route}` and prompts
- [MCP server card](https://oxarus.com/.well-known/mcp.json): transport, tools, resources and prompts of the MCP server
- [API catalog](https://oxarus.com/.well-known/api-catalog): RFC 9727 linkset pointing to the API description and documentation
## Optional
- [Hizmetler (eski adres)](https://oxarus.com/tr/services): redirects to /hub
---
title: "Software, product and financial engineering · Oxarus"
description: "Corporate sites, AI search visibility, e-commerce and custom systems. Oxarus Studio builds web and mobile products; Oxarus Quant builds market software."
url: https://oxarus.com/en
key: home
route: /
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr
en: https://oxarus.com/en
documents:
json: https://oxarus.com/machine/en/home.json
jsonld: https://oxarus.com/machine/en/index.jsonld
txt: https://oxarus.com/machine/en/index.txt
schema: oxarus.machine/2.0
---
# Software, product and financial engineering · Oxarus
> Corporate sites, AI search visibility, e-commerce and custom systems. Oxarus Studio builds web and mobile products; Oxarus Quant builds market software.
Breadcrumbs: [Oxarus home](https://oxarus.com/en)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [creative universe.](#hero)
- [one roof.](#units)
- [find the problem that sounds like yours.](#help)
- [WHY OXARUS](#manifesto)
- [where would you like to start?](#paths)
## creative universe.
_AUTHORITY_
- [Start your project](https://oxarus.com/en/contact#start) → `start_project_brief()`
- [See the units](https://oxarus.com/en#units-heading) → `open_page(path="/", anchor="units-heading")`
- **Software for companies** · _hub._
Corporate sites, AI search, e-commerce and dashboards built for your company.
- [Explore Hub](https://oxarus.com/en/hub)
- **Product and app engineering** · _studio._
We run our own product, Pals, on EduNeta, and design and build web and mobile products for brands.
- [Explore Studio](https://oxarus.com/en/studio)
- **Forex and market engineering** · _quant._
L.I.T. brings global market data onto one screen, and we build systematic models with our own capital.
- [Explore Quant](https://oxarus.com/en/quant)
_Representative interface data_ · Representative interfaces.
- **time:** 9:41
Home · Menu · Rewards · Profile
- **brand:** Brewline
- **hello:** Good morning, Sophia
- **store:** Karaköy branch · 350 m
**Preparing your order**
- **item:** Flat White · Medium
- **eta:** 4 min
1. Received
2. Preparing
3. Ready for pickup
- **points:** 6 / 8 coffees
- **reward:** 2 more and the next one's on us
- **menuTitle:** Today's picks
Hot · Iced · Bakery
- **Flat White**
- **price:** ₺135
> Double shot
- **Cortado**
- **price:** ₺120
> With oat milk
- **Cold Brew**
- **price:** ₺145
> 18-hour steep
- **cart:** View cart
_Representative interface data_ · Representative interfaces.
**L.I.T.**
> Live feed
Strength matrix · Intelligence feed · Macro calendar
> Representative screen. Not investment advice.
- **brandSub:** MARKET INTELLIGENCE
- **clock:** 14:26:08
- **tz:** GMT+3
| | | |
| --- | --- | --- |
| EUR/USD | 1.0842 | +0.12 |
| GBP/USD | 1.2718 | -0.08 |
| USD/JPY | 151.34 | +0.21 |
| XAU/USD | 2,386.4 | +0.34 |
| AUD/USD | 0.6581 | -0.15 |
| USD/CHF | 0.9036 | +0.05 |
**Currency strength matrix**
- **sub:** 8 majors · 4-hour window
| | | | |
| --- | --- | --- | --- |
| USD | US dollar | 82 | STRONG |
| CHF | Swiss franc | 71 | STRONG |
| EUR | Euro | 58 | NEUTRAL |
| GBP | British pound | 54 | NEUTRAL |
| CAD | Canadian dollar | 47 | NEUTRAL |
| AUD | Australian dollar | 36 | WEAK |
| NZD | New Zealand dollar | 29 | WEAK |
| JPY | Japanese yen | 18 | WEAK |
**Intelligence feed**
- **sub:** Sources merged, impact tagged
- **Powell: rate path will stay data-dependent** · _HIGH IMPACT_ · _2 min_
- **src:** Fed
- **Lagarde offers no guidance for June meeting** · _HIGH IMPACT_ · _11 min_
- **src:** ECB
- **Japan hardens its intervention rhetoric** · _MEDIUM_ · _24 min_
- **src:** BoJ
- **Crude inventories come in below expectations** · _MEDIUM_ · _38 min_
- **src:** EIA
**US core CPI (MoM)**
- **catalyst:** NEXT CATALYST
- **meta:** 15:30 GMT+3 · USD · high impact
HR · MIN · SEC
ACTUAL · FORECAST · PREVIOUS
- **Eurozone CPI** · _12:00_
- **ccy:** EUR
- **actual:** 2.4
- **forecast:** 2.5
- **previous:** 2.6
- **UK unemployment rate** · _10:00_
- **ccy:** GBP
- **actual:** 4.3
- **forecast:** 4.2
- **previous:** 4.2
**Market context**
- **sentiment:** Risk appetite
- **sentimentValue:** Cautious
- Risk-off
- Risk-on
**Sessions**
| | |
| --- | --- |
| Tokyo | Closed |
| London | Open |
| New York | Opening |
**Volatility · 1h**
| | |
| --- | --- |
| XAU | 78 |
| JPY | 64 |
| GBP | 41 |
| EUR | 33 |
- **resume:** Auto
_Representative interface data_ · Representative interfaces.
**Showcase**
- **search:** Search brands or sectors
- **open:** View
- **all:** All
- **corporate:** Corporate
- **commerce:** E-commerce
- **clinic:** Clinics
- **hotel:** Hotels
- **food:** Food & drink
**A quiet Aegean escape.**
- **sector:** Boutique hotel
- **cta:** Book a stay
**Every shipment, tracked live.**
- **sector:** Logistics
- **cta:** Track
**Light, stone and space.**
- **sector:** Architecture studio
- **cta:** Projects
**Furniture for slow living.**
- **sector:** Furniture store
- **cta:** Collection
**Clear counsel for complex cases.**
- **sector:** Law firm
- **cta:** Get advice
**Roast of the week**
- **sector:** Coffee roaster
- **cta:** Add to cart
**One night closer to the summit.**
- **sector:** Mountain lodge
- **cta:** Rooms
**A clear plan for a calm smile.**
- **sector:** Dental clinic
- **cta:** Book a visit
**Solid ground, on-time handover.**
- **sector:** Construction
- **cta:** Projects
**The autumn edit**
- **sector:** Fashion label
- **cta:** Shop now
**The season's table.**
- **sector:** Bistro
- **cta:** Book a table
**Skin care, backed by science.**
- **sector:** Skin clinic
- **cta:** Book
## one roof.
_THREE UNITS_
Each unit has its own team and its own pages. Engineering discipline and infrastructure are shared.
- **Oxarus Hub** · _hub_
Software for companies
A site built for your brand, visibility in AI search, an online store and dashboards built around how you work.
- _Representative interface data_
> Site report
- Performance
- Accessibility
- SEO
98 · 100 · 100
- [Corporate web](https://oxarus.com/en/hub/corporate-web)
- [AI search](https://oxarus.com/en/hub/ai-search)
- [E-commerce](https://oxarus.com/en/hub/ecommerce)
- [Custom systems](https://oxarus.com/en/hub/custom-systems)
- [Go to Hub](https://oxarus.com/en/hub)
- **Oxarus Studio** · _studio_
Product and app engineering
We run our own product, Pals, on EduNeta, and design and build web and mobile products for clients.
- _Representative interface data_
> Pals · EduNeta
Interface and interaction · Web dashboard · iOS app · Android app
- Done
- Live
- In review
- Live
- [Pals](https://oxarus.com/en/studio/pals)
- [App development](https://oxarus.com/en/studio/services)
- [Interaction design](https://oxarus.com/en/studio/design)
- [Mobile](https://oxarus.com/en/studio/mobile)
- [Go to Studio](https://oxarus.com/en/studio)
- **Oxarus Quant** · _quant_
Market engineering
The L.I.T. terminal, custom MT5 robots and measurable research. We work with our own capital, so every rule applies to us first.
- _Representative interface data_
> Strength matrix
- EURUSD
- GBPUSD
- USDJPY
- XAUUSD
- M15
- H1
- H4
- D1
- [L.I.T. terminal](https://oxarus.com/en/quant/lit)
- [MT5 robots](https://oxarus.com/en/quant/robots)
- [Research](https://oxarus.com/en/quant/research)
- [Engineering](https://oxarus.com/en/quant/engineering)
- [Go to Quant](https://oxarus.com/en/quant)
> Representative
_Interface labels:_ Explore
## find the problem that sounds like yours.
_HUB · HOW WE HELP_
Companies usually come to us with a problem. The four situations below are representative scenarios drawn from work we see often. Pick the closest one to see what we look at, what we do and what you keep.
- _3–5 weeks_
- **audience:** Corporations, holding companies, professional services firms
- **solution:** Corporate web
Our website makes us look smaller than we are.
The site was built years ago on an off-the-shelf theme. It loads slowly, falls apart on phones, and every update means emailing someone. Visitors can't see the company's real scale on the first screen.
**What we do**
- We clarify together what the company wants to say and who it's talking to
- We build a brand-specific design for phones first, then for desktop
- We hand over a content editor simple enough for your team to use
**What you keep**
- A site designed just for you
- A content editor your team uses
- Redirects from old URLs to the new pages
- Source code and design files
- _First report in week 1 · monthly tracking_
- **audience:** Clinics, law firms, local businesses, B2B service firms
- **solution:** AI search
Customers ask ChatGPT, and it doesn't recommend us.
Information about the company online is inconsistent and incomplete: services aren't clear on the site, the Google profile is outdated, and directory listings don't match. AI won't recommend a business it isn't sure about.
**What we do**
- We ask ChatGPT, Gemini and Perplexity the questions your customers might ask, and record the answers
- We make the information on your site, Google profile and directories consistent and correct
- Every month we ask the same questions again and report what changed
**What you keep**
- Baseline visibility report
- Corrected site and profile information
- Content pages that answer customer questions
- Monthly visibility report
- _6–10 weeks_
- **audience:** Online brands, manufacturers, wholesalers
- **solution:** E-commerce
We're selling, but every order is tracked by hand.
Store, marketplace, shipping and accounting all live in separate places. Stock drops in one but not the other, and the same details get retyped every day for invoices and shipping labels.
**What we do**
- We map the path an order takes from payment to invoice
- We build a store for your brand, connected to payments, shipping and marketplaces
- If you're on an existing platform, we migrate products, customers and orders without loss
**What you keep**
- A custom online store
- Payment, shipping, marketplace and e-invoice integrations
- Stock and order management dashboard
- Migration and verification report
- _8–10 weeks_
- **audience:** SMBs with growing operations, companies with field teams
- **solution:** Custom systems
Everything lives in Excel and WhatsApp groups.
As the business grew, spreadsheets multiplied and approvals got lost in chat. The same information is entered in several places, and who did what only becomes clear at the end of the day.
**What we do**
- Together with your team, we find the task that wastes the most time
- We move that work into a single dashboard with screens designed for each role
- We automate the repetitive steps and connect them to accounting
**What you keep**
- A management dashboard built for your company
- Automated notification and approval flows
- Migration of your Excel data
- User training and support
_Representative interface data_
- **page:** Home
**Today**
- **welcome:** Welcome to our website
- **loading:** Loading
- Off-the-shelf theme
- Breaks on phones
- Updates by email
**Solid foundations, delivered on time.**
- **brand:** Armelon
- **cta:** Projects
- **editor:** Content editor
- **draft:** New project: Harbour residences
- **publish:** Publish
- **published:** Live
- Brand-specific design
- Phone first
- Your team runs the editor
**A good dental clinic in Kadıköy?**
- **answer:** Top clinics:
- **brand:** Your clinic
- Orlesa Dental
- Tuvena Dental
- Lirva Oral Care
- **sourcesLabel:** What the assistant found
**Today**
- **missing:** Your clinic isn't in the answer
**What the assistant found**
- Site: services unclear
- Google profile: old address
- Directories: different phone
**After**
- **badge:** Recommended
**What the assistant found**
- Site: services clear
- Google profile: current
- Directories: consistent
- Store
- Marketplace
- Shipping
- Accounting
- **stock:** Stock
**Today**
- **manual:** Typed by hand
- **mismatch:** Stock doesn't match
**After**
1. Order
2. Payment
3. Shipping label
4. e-Invoice
5. Stock updated
- **synced:** Same stock on every channel
**Today**
- 0
- **source:** Excel
- **text:** quote\_final\_FINAL.xlsx
- 1
- **source:** WhatsApp
- **text:** Who approved this quote?
- 2
- **source:** Email
- **text:** Fwd: Fwd: price list
- **lost:** The approval got lost in chat
**One dashboard**
- Record
- Owner
- Status
| | | |
| --- | --- | --- |
| Quote #218 | Sales | Approved |
| Service job #74 | Field team | On the way |
| Invoice #1043 | Accounting | Issued |
_Interface labels:_ Four representative scenarios · Representative scenario · What we see · Timeline · Solution details · Before and after · Previous scenario · Next scenario
## WHY OXARUS
Our own products are live every day. In them we see what a slow page, a badly built flow or a careless screen costs the people using it. We build your work from scratch around the rules of your business and deliver it with the care we give our own products.
- live every day
- costs the people using it
- from scratch
**Our products and our work**
- **Pals** · _Studio_
Our own learning product. Students, parents and teachers see the same information on their own screens, on web, iOS and Android.
- **status:** Live at EduNeta
- [Explore Pals](https://oxarus.com/en/studio/pals)
- **L.I.T.** · _Quant_
Our market product that brings news, the economic calendar and correlations into one terminal.
- **status:** Early access
- [See L.I.T.](https://oxarus.com/en/quant/lit)
- **Showcase** · _Hub_
Sites, systems and apps we built for the brands we work with.
- **status:** Selected work
- [Go to the showcase](https://oxarus.com/en/showcase)
## where would you like to start?
_LET'S BEGIN_
Pick a path or write to us directly; together we'll route your need to the right team.
- **A project for my company** · _hub_
A site, a store, a dashboard or AI visibility.
- [Explore Hub](https://oxarus.com/en/hub)
- **Build an app or a product** · _studio_
Web and mobile product development, from idea to launch.
- [Explore Studio](https://oxarus.com/en/studio/services)
- **Automate my processes** · _agent_
Hand invoice, email and document workflows over to agents.
- [Explore Agent AI](https://oxarus.com/en/automation)
- **L.I.T. waitlist** · _quant_
A terminal that tracks global market data on one screen.
- [See L.I.T.](https://oxarus.com/en/quant/lit)
**A short note is enough.**
_DIRECT CONTACT_
Tell us in a few sentences what you want to do. The team that receives your message reads it and, if needed, connects you with the right person.
- [Send an email](mailto:info@oxarus.com) → `contact()`
**Process**
1. We read your message
2. We have a short intro call
3. We send scope and a quote in writing
- [Fill in the project form](https://oxarus.com/en/contact#start) → `start_project_brief()`
A few questions that clarify what you need and route it to the right unit.
- **or:** or by email
_Interface labels:_ Copy address · Copied
## Actions
- [Start your project](https://oxarus.com/en/contact#start) → `start_project_brief()`
- [See the units](https://oxarus.com/en#units-heading) → `open_page(path="/", anchor="units-heading")`
- [Send an email](mailto:info@oxarus.com) → `contact()`
- [Türkçe](https://oxarus.com/tr) → `switch_locale(locale="tr", path="/")`
## Related pages
- [Oxarus Hub](https://oxarus.com/en/hub)
- [Oxarus Studio](https://oxarus.com/en/studio)
- [Oxarus Quant](https://oxarus.com/en/quant)
- [Oxarus Agent AI](https://oxarus.com/en/automation)
- [Showcase](https://oxarus.com/en/showcase)
- [Careers](https://oxarus.com/en/careers)
- [Contact](https://oxarus.com/en/contact)
- [Privacy Policy](https://oxarus.com/en/legal/privacy)
- [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
- [Terms of Use](https://oxarus.com/en/legal/terms)
- [Cookie Policy](https://oxarus.com/en/legal/cookies)
- [Company Information](https://oxarus.com/en/legal/company)
---
title: "Websites, AI search, e-commerce and custom systems"
description: "Brand websites, AI search visibility, online stores and custom dashboards, delivered end to end on a clear timeline. The code is yours."
url: https://oxarus.com/en/hub
key: hub
route: /hub
unit: hub
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/hub
en: https://oxarus.com/en/hub
documents:
json: https://oxarus.com/machine/en/hub.json
jsonld: https://oxarus.com/machine/en/hub.jsonld
txt: https://oxarus.com/machine/en/hub.txt
schema: oxarus.machine/2.0
---
# Websites, AI search, e-commerce and custom systems
> Brand websites, AI search visibility, online stores and custom dashboards, delivered end to end on a clear timeline. The code is yours.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Hub](https://oxarus.com/en/hub)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [four solutions, end to end.](#hero)
- [start with what you need most.](#index)
- [all four share one foundation.](#connect)
- [what's slowing you down most today?](#finder)
- [HOW WE WORK](#principles)
- [let's talk business.](#cta)
## four solutions, end to end.
_OXARUS HUB_
A corporate site, visibility in AI search, an online store and dashboards built for your company. We design, build and connect them all.
- [Get in touch](https://oxarus.com/en/hub#cta-heading) → `open_page(path="/hub", anchor="cta-heading")`
- [See solutions](https://oxarus.com/en/hub#index-heading) → `open_page(path="/hub", anchor="index-heading")`
- One point of contact, end-to-end delivery
- Code and design files are yours
- A clear timeline from day one
1. Corporate web
2. AI search
3. E-commerce
4. Custom systems
- [Corporate web](https://oxarus.com/en/hub/corporate-web)
- [AI search](https://oxarus.com/en/hub/ai-search)
- [E-commerce](https://oxarus.com/en/hub/ecommerce)
- [Custom systems](https://oxarus.com/en/hub/custom-systems)
_Representative interface data_ · Representative interfaces.
- **aiTab:** ChatGPT
_Representative interface data_ · Representative interfaces.
- **tabTitle:** Linea Architects
- Linea Architects
- Projects · Linea Architects
- Bodrum House · Linea Architects
- **brand:** linea
- **brandSub:** architects
Projects · Office · Publications · Contact
**We design light.**
- **kicker:** Istanbul · Bodrum · Lisbon
- **counter:** 01 / 04
- **project:** Bodrum House, 2025
All · Residential · Cultural · Office
**Projects**
- **Bodrum House** · _Residential · 2025_
- **Aegean Villa** · _Residential · 2024_
- **City Museum** · _Cultural · 2023_
- **Forest House** · _Residential · 2022_
**Bodrum House**
- **back:** Projects
- **text:** Three volumes set into the hillside see the sea from a different angle at every hour of the day. Local stone and timber are sheltered by deep eaves suited to the hot climate.
- **cta:** Let's talk about a similar project
- **Year:** 2025
- **Area:** 420 m²
- **Location:** Bodrum, Muğla
- **Status:** Completed
- **New project inquiry:** Villa · Çeşme · 600 m²
_Representative interface data_ · Representative interfaces.
- **question:** Can you recommend a good dental clinic in Kadıköy?
_Representative interface data_ · Representative interfaces.
- **engine:** ChatGPT
- **you:** You
- **tabBefore:** Today
- **tabAfter:** With Oxarus
- **replay:** Replay answer
- **askPlaceholder:** Ask ChatGPT anything
- **status:** Searching the web
- **beforeAnswer:** Three clinics with strong reviews stand out in Kadıköy:
1. Moda Dental Care: implants and cosmetic dentistry
2. Bahariye Dental: pediatric dentistry, open on weekends
3. Kalamış Dental Studio: clear aligners and orthodontics
- **afterAnswer:** Three clinics stand out in Kadıköy:
1. Smile Atelier Dental: implants and clear aligners, open Saturdays, rated 4.9
2. Moda Dental Care: implants and cosmetic dentistry
3. Bahariye Dental: pediatric dentistry, open on weekends
- **beforeChip:** Your business isn't in this answer
- **afterChip:** Source: Smile Atelier Dental website and Google profile
- **afterSource:** 2 sources
_Representative interface data_ · Representative interfaces.
- **storeName:** dune atelier
- **tabTitle:** {page} · dune atelier
- **home:** Bestsellers
- **product:** Stone mug
- **checkout:** Secure checkout
- **Done:** Order confirmed
- **announcement:** Free shipping on orders over {amount} · Free 14-day returns
New arrivals · Bestsellers · Mugs · Tableware · Our story
- **search:** Search products
- Home
- Bestsellers
- **homeCount:** {count} products
- **sort:** Sort: Featured
- **filters:** Filter
- **clearFilters:** Clear
- **categoryLabel:** Category
- Mugs
- Tableware
- Textiles
- **priceLabel:** Price
- **inStockOnly:** In stock only
**{discount} off stone mugs**
- **eyebrow:** Autumn edit
- **cta:** Shop mugs
- **Stone mug**
- **Stone mug**
- **Linen napkin set**
- **Serving plate**
- **bestseller:** Bestseller
- **lowStock:** Only {count} left
- **quickAdd:** Quick add
- Home
- Mugs
- Stone mug
- **product:** Stone mug
- **productMeta:** Handmade ceramic · 350 ml · Dishwasher safe
- **reviews:** {count} reviews
- **installment:** {count} installments of {amount} · No extra charge
- **colorLabel:** Color
- Sand
- Charcoal
- Mist
- **inStock:** In stock · ships tomorrow
- **soldOut:** Sold out · we'll let you know
- **soldOutBadge:** Sold out
- **qtyLabel:** Qty
- **addToCart:** Add to cart
- **added:** Added to cart
- **notify:** Notify me
- Ships tomorrow
- Free 14-day returns
- Secure checkout
**Your cart**
- **Stone mug**
- **Linen napkin set**
- **itemCount:** {count} items
- **freeShipping:** You've unlocked free shipping
- **freeShippingFrom:** Over {amount}
- **upsellLabel:** Goes well with
- **Goes well with:** Add
- **coupon:** Discount code
- **subtotal:** Subtotal
- **Delivery:** Shipping
- **free:** Free
- **total:** Total
- **vatIncluded:** VAT included
- **checkoutCta:** Checkout
- Cart
- Delivery
- Payment
- **secure:** Secure checkout
- **addressLabel:** Deliver to
- **Deliver to:** Elif Yıldız
- **Deliver to:** Moda, Kadıköy · Istanbul
- **Delivery:** Standard · Aras Kargo · 2–3 business days
- **edit:** Change
- **paymentLabel:** Payment
- **Installments:** Pay in full or in installments.
- Card
- Bank transfer
- Cash on delivery
- **cardNumber:** Card number
- **expiry:** Expiry
- **cvc:** CVC
- **single:** Pay in full
- **installmentCount:** {count} installments
- **perMonth:** {amount} a month
- **consent:** I accept the pre-contract information and the distance sales agreement.
- **pay:** Pay with 3D Secure
- **paying:** Your bank is verifying
**Thank you, Elif!**
- **order:** Order no. {number}
- **body:** A confirmation email and text are on their way. We'll send the tracking number as soon as the parcel ships.
- **nextTitle:** What happens on its own after the order
1. **Payment approved** · _iyzico · 3D Secure_
2. **e-Archive invoice issued** · _Paraşüt_
3. **Shipping label ready** · _Aras Kargo · ships tomorrow_
4. **Stock updated** · _Site, Trendyol, Hepsiburada and Amazon_
- **pending:** Queued
**Create your account in one step**
- **body:** Follow your orders and returns in one place.
- **cta:** Set a password
- **summary:** Order summary
- **paidWith:** Card · Paid in full
- **eta:** Estimated delivery
- **etaValue:** 2–3 business days
**Track your order**
- **code:** Aras Kargo · 7184 2290 13
1. Placed
2. Preparing
3. Shipped
4. Delivered
- **cta:** Track
- **todayLabel:** Today's revenue
- **ordersLabel:** {count} orders
- **tag:** Representative
- **Marketplace order**
- **text:** {order} · Hepsiburada
- **Price sync**
- **text:** Same price on 4 channels
- **Cart**
- **text:** {count} items · free shipping
- **Payment**
- **text:** Waiting for 3D Secure
- **New order**
- **text:** {order} · Site · Kadıköy
- **Stock updated**
- **text:** Stone mug, Sand · {from} → {to}
_Representative interface data_ · Representative interfaces.
- **tabTitle:** Dashboard · Northfield Supply
- **excelName:** order\_tracking\_FINAL\_v3.xlsx
| | | |
| --- | --- | --- |
| Customer | Product | Status |
| Yıldız İnşaat | Plaster 40 bags | ?? |
| Ece Mimarlık | Tiles 60 m² | shipped?? |
| Demir Usta | Paint 12 buckets | CALL |
- **whatsappName:** Warehouse · Hakan
- Did Yıldız's plaster go out?
- Think we're down to 20
- Call Ece back!
- Invoice not sent yet?
- **mailSubject:** RE: RE: RE: stock status
- **mailFrom:** accounting@
- **company:** Northfield Supply
Dashboard · Orders · Inventory · Customers · Service · Reports
- **greeting:** Good morning, Murat
- **date:** Monday, September 14
- **Orders today**
- **value:** 24
- **delta:** +6
- **Awaiting approval**
- **value:** 3
- **Low stock**
- **value:** 5
- **Open service jobs**
- **value:** 7
- **delta:** -2
**Recent orders**
- 0
- **no:** #2041
- **customer:** Yıldız İnşaat
- **item:** Plaster · 40 bags
- **amount:** ₺18,400
- **status:** New
- 1
- **no:** #2040
- **customer:** Ece Mimarlık
- **item:** Tiles · 60 m²
- **amount:** ₺42,900
- **status:** In transit
- 2
- **no:** #2039
- **customer:** Demir Usta
- **item:** Paint · 12 buckets
- **amount:** ₺9,360
- **status:** Preparing
- 3
- **no:** #2038
- **customer:** Kaya Dekorasyon
- **item:** Parquet · 85 m²
- **amount:** ₺61,200
- **status:** Delivered
- **new:** New
- **transit:** In transit
- **preparing:** Preparing
- **delivered:** Delivered
**This week**
- Mo
- Tu
- We
- Th
- Fr
- Sa
62 · 78 · 54 · 88 · 96 · 40
**Automation · New order**
1. **Order received** · _Web form · Yıldız İnşaat_
2. **Stock reserved** · _Plaster · 40 bags, 180 left_
3. **Warehouse work order** · _Added to Hakan's list_
4. **Invoice draft** · _Sent to Logo_
5. **SMS to customer** · _“Your order is being prepared”_
- **toast:** Work order #2041 sent to the warehouse
- **auto:** Automatic
_Interface labels:_ Explore this solution
## start with what you need most.
_SOLUTIONS_
Four solutions on shared engineering. Pick one to see how it works on screen and what we deliver.
- **Corporate web**
A site designed for your brand that loads in under a second and is easy for your team to update.
Design · Content editor · Multilingual
- [Corporate web](https://oxarus.com/en/hub/corporate-web)
- **AI search**
When customers ask ChatGPT, Gemini or Perplexity, make sure your name is in the answer.
Visibility report · Google profile · Monthly tracking
- [AI search](https://oxarus.com/en/hub/ai-search)
- **E-commerce**
A custom store, a dealer portal and lossless migration from off-the-shelf platforms.
Payments and shipping · Marketplaces · B2B
- [E-commerce](https://oxarus.com/en/hub/ecommerce)
- **Custom systems**
One dashboard and self-running steps for work that lives in Excel, WhatsApp and paper.
Orders and stock · Customer tracking · Automation
- [Custom systems](https://oxarus.com/en/hub/custom-systems)
- **deliver:** What you get
_Representative interface data_ · Representative
**Content editor**
- **brand:** Linea Architects
- **editing:** Home page · featured project
- **projectLabel:** Project
- **languageLabel:** Language
- EN
- TR
- 0
- Bodrum House
- Bodrum Evi
- Residential · 2025
- Konut · 2025
- 1
- Aegean Villa
- Ege Villası
- Residential · 2024
- Konut · 2024
- 2
- City Museum
- Kent Müzesi
- Cultural · 2023
- Kültür · 2023
| | | |
| --- | --- | --- |
| Projects | Office | Contact |
| Projeler | Ofis | İletişim |
- Istanbul · Bodrum · Lisbon
- İstanbul · Bodrum · Lizbon
- View project
- Projeyi görün
- **publish:** Publish
- **publishing:** Publishing
- **draft:** {count} unpublished changes
> Live on the site
**Visibility check**
- **brand:** Smile Atelier Dental
- **question:** Can you recommend a good dental clinic in Kadıköy?
- **assistants:** Assistants
- **before:** Today
> After the fixes
- **you:** You
- **missing:** Not in the answer
- **rank:** Ranked {rank}
- **summary:** Named by {count} of {total} assistants
- **Smile Atelier Dental**
- **detail:** implants and clear aligners, open Saturdays
- **Moda Dental Care**
- **detail:** implants and cosmetic dentistry
- **Bahariye Dental**
- **detail:** pediatric dentistry, open on weekends
- **Kalamış Dental Studio**
- **detail:** clear aligners and orthodontics
**Orders and stock**
- **brand:** dune atelier
- **simulate:** New order
- **revenue:** Today's revenue
- **Latest orders:** Orders
**Stock**
> One stock, four channels
- Site
- Trendyol
- Hepsiburada
- Amazon
- **Stone mug**
- **color:** Sand
- **Stone mug**
- **color:** Charcoal
- **Linen napkin set**
- **color:** Sand
- **Serving plate**
- **color:** Mist
- Ankara
- Izmir
- Bursa
- Antalya
- Eskişehir
- Kayseri
- Trabzon
- Konya
- **synced:** Updated on all four channels
- **out:** Sold out
**Order flow**
- **brand:** Northfield Supply
- **advance:** Next step
- **done:** Delivered
1. New
2. Preparing
3. In transit
4. Delivered
- **no:** #2041
- **customer:** Yıldız İnşaat
- **item:** Plaster · 40 bags
- **amount:** ₺18,400
- 0
- **no:** #2039
- **customer:** Demir Usta
- **item:** Paint · 12 buckets
- 1
- **no:** #2040
- **customer:** Ece Mimarlık
- **item:** Tiles · 60 m²
- 2
- **no:** #2038
- **customer:** Kaya Dekorasyon
- **item:** Parquet · 85 m²
- **logTitle:** Done automatically
| | |
| --- | --- |
| Order opened from the web form | 40 bags reserved in stock |
| Picking order sent to the warehouse | |
| Delivery note issued | Customer told the order is on its way |
| Delivery photo added to the order | E-invoice issued and sent to accounting |
_Interface labels:_ Explore the page · Play again
## all four share one foundation.
_WORKS TOGETHER_
The solutions are built on shared infrastructure. A request from your site becomes a task in the dashboard, product data is published in a form AI can read, and stock stays the same on every channel.
- **center:** Your site
- **center sub:** Flows start here
> Representative
- **AI search** · _llms.txt · schema_
Your content is published so ChatGPT and Google read it correctly
- _Representative interface data_
1. 0
- **system:** Site
- **text:** New service page published
2. 1
- **system:** Schema
- **text:** Structured data updated
3. 2
- **system:** ChatGPT
- **text:** Page shown as a source in the answer
- [Explore AI search](https://oxarus.com/en/hub/ai-search)
- **E-commerce** · _4 channels · one stock_
Products, prices and stock match on your site and marketplaces
- _Representative interface data_
1. 0
- **system:** Store
- **text:** Two stone mugs sold on the site
2. 1
- **system:** Stock
- **text:** Stock went from 26 to 24
3. 2
- **system:** Marketplaces
- **text:** Trendyol, Hepsiburada and Amazon updated at the same moment
- [Explore e-commerce](https://oxarus.com/en/hub/ecommerce)
- **Custom systems** · _form → task_
Forms and orders land in the dashboard as tasks
- _Representative interface data_
1. 0
- **system:** Form
- **text:** Contact form submitted
2. 1
- **system:** Dashboard
- **text:** New task opened in the dashboard
3. 2
- **system:** Alert
- **text:** Assigned to sales, notification sent
- [Explore custom systems](https://oxarus.com/en/hub/custom-systems)
- **Accounting and ERP** · _e-invoice · ledger_
Invoices and account records are never keyed in by hand
- _Representative interface data_
1. 0
- **system:** Dashboard
- **text:** Order approved
2. 1
- **system:** e-Invoice
- **text:** E-invoice issued
3. 2
- **system:** ERP
- **text:** Posted to the customer account automatically
- [Explore integrations](https://oxarus.com/en/hub/custom-systems)
_Interface labels:_ Data flow · Pick a connection · Replay the flow
## what's slowing you down most today?
_WHERE TO START_
Pick one and we'll show you the right starting point.
- **Our site is old, slow and doesn't reflect our brand**
First impressions happen on your site. Start with Corporate web: a fast site built for your brand that your team can update.
- **Recommended starting point:** Corporate web
**First steps**
1. Discovery call and an audit of the current site
2. Design direction and page structure
3. Launch with the content editor
**Pairs well with**
AI search · Custom systems
- [Corporate web](https://oxarus.com/en/hub/corporate-web)
- **Customers can't find us in AI or on Google**
First we measure what ChatGPT, Gemini and Google show about you, then we fix what's missing.
- **Recommended starting point:** AI search
**First steps**
1. Audit across ChatGPT, Gemini and Google
2. A list of missing and incorrect information
3. Fixes and monthly tracking
**Pairs well with**
Corporate web
- [AI search](https://oxarus.com/en/hub/ai-search)
- **We want to sell online or grow our store**
Let's start with a custom store connected to payments and shipping, or a lossless migration if you're on an off-the-shelf platform.
- **Recommended starting point:** E-commerce
**First steps**
1. Mapping product, payment and shipping needs
2. Store design and integrations
3. Migration, testing and launch
**Pairs well with**
AI search · Custom systems
- [E-commerce](https://oxarus.com/en/hub/ecommerce)
- **Our work is scattered across Excel and WhatsApp**
We start with the task that wastes the most time and bring orders, stock and your team into one dashboard.
- **Recommended starting point:** Custom systems
**First steps**
1. Choosing the most time-consuming task together
2. The first module in a single dashboard
3. Automating the repetitive steps
**Pairs well with**
Corporate web · E-commerce
- [Custom systems](https://oxarus.com/en/hub/custom-systems)
If more than one fits, write to us in two sentences and we'll set the order together.
- [Get in touch](https://oxarus.com/en/hub#cta-heading) → `open_page(path="/hub", anchor="cta-heading")`
_Interface labels:_ Explore this solution
## HOW WE WORK
> Representative
- **no middlemen.**
Design, engineering and launch move under one accountable lead. The person doing the work answers your questions.
- **from:** You
**One point of contact**
**One point of contact**
- Design
- Engineering
- Launch
- Support
- **your code.** · _Handed over to your company_
When the project ends, source code, design files and data are handed over to your company. You're not tied to a license or to a single agency.
**Handover checklist**
**Handover checklist**
- Source code repository
- Design files
- Database backup
- Domain and accounts
- **clear timeline.**
At the end of the discovery call, we put scope, price and delivery date in writing. Every week, you see working progress.
- **now:** This week
- **weekly:** A working build every week
**Weekly progress**
**Weekly progress**
- Discovery
- Design
- Development
- Launch
## let's talk business.
_LET'S BEGIN_
Two sentences on what you do and what you want to change are enough. We'll pick the right path together.
- [Get in touch](mailto:info@oxarus.com) → `contact()`
_Interface labels:_ Copied
## Actions
- [Get in touch](https://oxarus.com/en/hub#cta-heading) → `open_page(path="/hub", anchor="cta-heading")`
- [See solutions](https://oxarus.com/en/hub#index-heading) → `open_page(path="/hub", anchor="index-heading")`
- [Get in touch](mailto:info@oxarus.com) → `contact()`
- [Türkçe](https://oxarus.com/tr/hub) → `switch_locale(locale="tr", path="/hub")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
- [Corporate Web](https://oxarus.com/en/hub/corporate-web)
- [AI Search](https://oxarus.com/en/hub/ai-search)
- [E-Commerce](https://oxarus.com/en/hub/ecommerce)
- [Custom Systems](https://oxarus.com/en/hub/custom-systems)
---
title: "Corporate website and digital platform development"
description: "Corporate websites on a modern, refined design architecture, built around your brand and updated by your own team. Multilingual structure included."
url: https://oxarus.com/en/hub/corporate-web
key: hub-corporate-web
route: /hub/corporate-web
unit: hub
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/hub/corporate-web
en: https://oxarus.com/en/hub/corporate-web
documents:
json: https://oxarus.com/machine/en/hub/corporate-web.json
jsonld: https://oxarus.com/machine/en/hub/corporate-web.jsonld
txt: https://oxarus.com/machine/en/hub/corporate-web.txt
schema: oxarus.machine/2.0
---
# Corporate website and digital platform development
> Corporate websites on a modern, refined design architecture, built around your brand and updated by your own team. Multilingual structure included.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Hub](https://oxarus.com/en/hub) › [Corporate Web](https://oxarus.com/en/hub/corporate-web)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [the site that tells your story.](#hero)
- [every layer of the site.](#deliverables)
- [design rules, written once.](#design)
- [your team publishes the news.](#editor)
- [every language gets its own page.](#languages)
- [measured before launch.](#quality)
- [the difference shows in year three.](#ledger)
- [modern, proven tools.](#tech)
- [four steps, clear timeline.](#process)
- [before we start.](#faq)
- [what grows with your site.](#others)
- [let's plan your new site.](#cta)
## the site that tells your story.
_HUB · CORPORATE WEB_
We deliver a corporate site designed around your brand, fast on phones, with content your team updates without touching code. No waiting on anyone for a small text change.
- [Start your project](https://oxarus.com/en/hub/corporate-web#contact-vault) → `open_page(path="/hub/corporate-web", anchor="contact-vault")`
- [What we deliver](https://oxarus.com/en/hub/corporate-web#services-grid) → `open_page(path="/hub/corporate-web", anchor="services-grid")`
- Live in 3–5 weeks
- Code and design files are yours
- Your team updates the content
1. Home
2. Projects
3. Project detail
_Representative interface data_ · Representative architecture firm website.
- **tabTitle:** Linea Architects
- Linea Architects
- Projects · Linea Architects
- Bodrum House · Linea Architects
- **brand:** linea
- **brandSub:** architects
Projects · Office · Publications · Contact
**We design light.**
- **kicker:** Istanbul · Bodrum · Lisbon
- **counter:** 01 / 04
- **project:** Bodrum House, 2025
All · Residential · Cultural · Office
**Projects**
- **Bodrum House** · _Residential · 2025_
- **Aegean Villa** · _Residential · 2024_
- **City Museum** · _Cultural · 2023_
- **Forest House** · _Residential · 2022_
**Bodrum House**
- **back:** Projects
- **text:** Three volumes set into the hillside see the sea from a different angle at every hour of the day. Local stone and timber are sheltered by deep eaves suited to the hot climate.
- **cta:** Let's talk about a similar project
- **Year:** 2025
- **Area:** 420 m²
- **Location:** Bodrum, Muğla
- **Status:** Completed
- **New project inquiry:** Villa · Çeşme · 600 m²
**Lighthouse report**
> Representative
- **Performance:** 99
- **Accessibility:** 100
- **Best practices:** 100
- **SEO:** 100
- **Load (LCP):** 1.2 s
- **Shift (CLS):** 0.02
## every layer of the site.
_WHAT WE DELIVER_
On a corporate site, design, content, languages, speed, search and security depend on each other. We build all six together and hand them over working. Each card takes you to a live example of that layer below.
- **Design built for your brand** · _DESIGN_
No off-the-shelf themes. We turn your colors, typefaces and photography style into design rules and design page by page. Phone first, then desktop.
- [Try the design system](https://oxarus.com/en/hub/corporate-web#design-heading) → `open_page(path="/hub/corporate-web", anchor="design-heading")`
- **Easy content management** · _CMS_
Your team updates news, announcements, job posts and page copy without touching code. The design is locked, so the layout never breaks.
- [Try the editor](https://oxarus.com/en/hub/corporate-web#editor-heading) → `open_page(path="/hub/corporate-web", anchor="editor-heading")`
- **Multiple languages** · _LANGUAGE_
Each language gets its own address and its own content, so search engines show the right language to visitors in the right country.
- [See the page tree](https://oxarus.com/en/hub/corporate-web#languages-heading) → `open_page(path="/hub/corporate-web", anchor="languages-heading")`
- **Pages that load fast** · _SPEED_
Pages are prebuilt, images are resized for each device and no unnecessary code is loaded. Core Web Vitals are measured before launch.
- [See the measurements](https://oxarus.com/en/hub/corporate-web#quality-heading) → `open_page(path="/hub/corporate-web", anchor="quality-heading")`
- **Google and AI** · _SEARCH_
Titles, descriptions and structured data tags are added, so search engines and AI tools read the facts on the page instead of guessing.
- [See the tags](https://oxarus.com/en/hub/corporate-web#quality-heading) → `open_page(path="/hub/corporate-web", anchor="quality-heading")`
- **Plugin-free, easy to maintain** · _SECURITY_
No pile of plugins waiting for updates. SSL, backups and security headers come built in from day one.
- [Compare year by year](https://oxarus.com/en/hub/corporate-web#ledger-heading) → `open_page(path="/hub/corporate-web", anchor="ledger-heading")`
## design rules, written once.
_DESIGN SYSTEM_
Color, typeface and corner radius are design variables. When one value changes, every component from the menu to the project card updates by the same rule. Try three directions for Linea Architects below.
- **Sign-off on a clickable prototype**
Before any code is written, you approve the pages by clicking through them on a phone and on a desktop.
- **Design files handed over to you**
The design files and the list of design variables stay with your company when the project ends.
- **Components that follow your brand guidelines**
Buttons, forms, cards and menus are designed once to your brand guidelines, and new pages are built from these parts.
_Representative interface data_ · Representative
**Design system**
- **subtitle:** Linea Architects
> Representative
- **reset:** Reset
- **paletteLabel:** Color
- Sand
- Night
- Olive
- **typeLabel:** Headings
- Serif
- Grotesk
- **radiusLabel:** Corners
- Sharp
- Soft
- Round
- **tokensLabel:** Design variables
- **viewLabel:** View
- **desktop:** Desktop
- **mobile:** Phone
- **applied:** Every component updated
- **pageName:** Home · Linea Architects
- Menu behind one button
- 44 px touch targets
**We design light.**
- **brand:** linea
- **brandSub:** architects
Projects · Office · Publications
- **kicker:** Istanbul · Bodrum · Lisbon
- **body:** Homes and cultural buildings shaped by the hillside, the sea and the forest.
- **primary:** Let's talk
- **secondary:** View projects
**Recent projects**
- **Forest House** · _Residential · 2022_
- **City Museum** · _Cultural · 2023_
- **Aegean Villa** · _Residential · 2024_
- **componentsLabel:** Components
- **tag:** All projects
- **inputPlaceholder:** Your email address
## your team publishes the news.
_CONTENT EDITOR_
News, announcements and job posts go into separate fields: title, category, cover image and summary. Typefaces, colors and layout are not in the editor, so the layout never breaks. Change the news item on the left and the page on the right updates as you type.
- **Draft, preview, publish**
A change shows up in the preview first and goes live on the site when you publish it.
- **Role-based access**
An editor prepares the draft and an approver publishes it. You decide who can change what.
- **Images resize themselves**
Even a large photo taken on a phone does not slow the page down; each device gets its own image size.
- **Locked design**
Font sizes, colors and layout cannot be changed from the editor, so the site keeps its original look.
_Representative interface data_ · Representative
- **panelTitle:** Content editor
- Publications
- New item
> Representative
- **restart:** Reset
- **Aegean Villa shortlisted for an award:** Draft
- **changed:** Unpublished changes
- **published:** Live
**Title**
- **date:** Publish date
- **category:** Category
- **cover:** Cover image
- **summary:** Summary
- Award
- Project
- Office
- Seaside
- Sunset
- Concrete facade
- **counter:** {count}/{max}
- **locked:** Design locked
- Typeface
- Colors
- Layout
- **lockedHint:** These settings are part of the design and do not appear in the editor.
- **save:** Save draft
- **publish:** Publish
- **saved:** Draft saved
- **publishedToast:** News item published
- **livePage:** Live page
- **previewTag:** Preview
- **liveTag:** Live
**Publications**
- **name:** Publications · Linea Architects
- **brand:** linea
- **brandSub:** architects
Projects · Office · Publications · Contact
- **newBadge:** New
- **readMore:** Read more
**Aegean Villa shortlisted for an award**
- **summary:** The villa made the shortlist in the residential category.
**Aegean Villa among the residential projects of the year**
- **summary:** The jury shortlisted the seaside villa in the residential category. The project will be shown at the exhibition at the end of September.
- **City Museum facade drawings published**
- **category:** Project
- **Our Lisbon office has moved**
- **category:** Office
- **Forest House photographs added to the archive**
- **category:** Project
## every language gets its own page.
_MULTILINGUAL SITES_
Turkish, English and German pages are published at separate addresses and linked to each other. Someone searching from Germany finds the German page. A visitor who switches language stays on the same page in the new language instead of landing on the home page.
_Representative interface data_ · Representative
**Page tree**
- **subtitle:** Linea Architects · Turkish, English, German
> Representative
- **pages:** {count} pages
- **Türkçe**
- Ana sayfa
- Projeler
- Bodrum Evi
- Ofis
- İletişim
- **English**
- Home
- Projects
- Bodrum House
- Studio
- Contact
- **Deutsch**
- Startseite
- Projekte
- Haus Bodrum
- Büro
- Kontakt
- **untranslated:** Awaiting translation
**Pairs announced to search engines**
- **body:** Each page's code lists its counterparts in the other languages. A language without a translation is left out, and the page to open when nothing matches is named too.
- **defaultLabel:** If nothing matches
- **notListed:** No translation, not listed
> The language menu uses the same pairs. A visitor on Bodrum Evi who switches to EN lands on Bodrum House.
**Search result**
- **from:** Searcher's country
- Türkiye
- United Kingdom
- Germany
- **siteName:** Linea Architects
- İstanbul, Bodrum ve Lizbon'da konut ve kültür yapıları tasarlayan mimarlık ofisi.
- Architecture studio designing homes and cultural buildings in Istanbul, Bodrum and Lisbon.
- Architekturbüro für Wohn- und Kulturbauten in Istanbul, Bodrum und Lissabon.
- **match:** A page in the searcher's language exists: {language}
- **fallback:** This page has no German version yet, so the search engine shows the English page.
## measured before launch.
_SPEED, ACCESSIBILITY, SEARCH_
Every page is checked three ways before launch: how fast it opens on a phone, whether it works with a keyboard and a screen reader, and whether search engines and AI tools read its content correctly.
- **Core Web Vitals** · _SPEED_
Google's page experience metrics: when the main content appears, how quickly the page responds to a tap, and whether the layout shifts while loading.
- Images prepared for each screen size
- Fonts preloaded so text does not jump
- Pages built ahead of time
- **Usable by everyone** · _ACCESSIBILITY_
The site works with a keyboard and a screen reader, not only a mouse. Color contrast is checked against WCAG AA.
- A logical focus order
- Alt text on images
- Headings in order
- **Structured data** · _SEARCH_
Facts such as the company name, city, project and date are also written into the page as tags machines can read.
- Company and contact details
- Project, news and event tags
- Page path information
_Representative interface data_ · Representative
> Representative
- **replay:** Replay
**Load measurement**
- **subtitle:** Representative page · phone
- **frames:** Load frames
- **lcpLabel:** Main content visible
- **LCP**
- **label:** Main content appears
- **INP**
- **label:** Response to a tap
- **CLS**
- **label:** Layout shift
- **seconds:** {value} s
- **ms:** {value} ms
- **good:** Good
- **improve:** Needs improvement
- **poor:** Poor
- **sample:** Representative page
- **source:** The colored ranges are Google's Core Web Vitals thresholds; the white markers are the values of a representative page.
**Accessibility check**
- **subtitle:** Representative page · Bodrum House
- Focus order
- Contrast
- Alt text
- Headings
- **tab:** Press Tab
- **focusIdle:** Press Tab to move through the page with a keyboard
- **focusStep:** {step}/{total} · {name}
- Logo
- Projects
- Contact
- View project button
- Email field
- Heading text
- Body text
- Button label
- **ratio:** {ratio}:1
- **pass:** AA
- **alt:** Three-volume house set into a hillside at sunset
**Bodrum House**
- **brand:** linea
Projects · Contact
- **body:** Three volumes set into the hillside see the sea from a different angle at every hour of the day.
- **subheading:** Project details
- **cta:** View project
- **email:** Your email address
- **Year:** 2025
- **Area:** 420 m²
- **outline:** Heading outline
**Structured data**
- **subtitle:** Representative page · Bodrum House
- **off:** No tags
- **on:** Tagged
- **codeLabel:** Tags added to the page
- **emptyCode:** This page has no structured data. The search engine tries to guess the facts from the text.
- **readLabel:** What machines read
- **unknown:** Unclear
- **Company:** Linea Architects
- **City:** Istanbul
- **Project:** Bodrum House
- **Year:** 2025
- **Location:** Bodrum, Muğla
**Bodrum House · Linea Architects**
- **label:** Search result
- **body:** A home made of three volumes set into a hillside. Local stone and timber are sheltered by deep eaves.
- Linea Architects
- Projects
- Bodrum House
## the difference shows in year three.
_TEMPLATE OR CUSTOM_
An off-the-shelf theme looks cheap and fast on day one. As the site grows, so does the load of plugins, licenses and updates. Change the year and compare the maintenance screens of the two sites.
| Off-the-shelf theme | Topic | Custom-built site |
| --- | --- | --- |
| Resembles hundreds of sites using the same theme. | Look | Designed for your brand alone. |
| Slows down as themes and plugins pile up. | Load speed | Only the code the page needs is loaded. |
| Outdated plugins leave the door open. | Security | No plugins; the parts to update are few and known. |
| Complicated menus and the fear of breaking things. | Content updates | A simple editor with only the fields you need. |
| Theme, plugin and license renewals. | Annual cost | No licenses; just hosting, plus support if you want it. |
| You depend on the theme and plugin vendors. | Ownership | Code and design files are entirely yours. |
_Representative interface data_ · Representative
> Representative
- **yearLabel:** Site age
- Launch day
- Year 1
- Year 3
**Theme-based site**
- **subtitle:** Admin panel · plugins
- Page builder
- Form plugin
- Multilingual plugin
- SEO plugin
- Gallery plugin
- Cache plugin
- **ok:** Up to date
- **update:** Update available
- **license:** License renewal
- **conflict:** Incompatible
- **installed:** Installed plugins
- **pending:** Pending tasks
- **more:** +{count} more
- **clear:** No warnings
- **conflicts:** {count} plugins are incompatible with the theme; updating may break the site.
**Custom-built site**
- **subtitle:** Maintenance log
- **installed:** Installed plugins
- **pending:** Pending tasks
- **pendingNone:** None
- _Launch day_
- **text:** Site launched
- _Launch day_
- **text:** Daily backups started
- _Launch day_
- **text:** SSL and security headers checked
- _Year 1_
- **text:** Careers page added
- _Year 1_
- **text:** Restore from backup tested
- _Year 1_
- **text:** Dependencies updated, tests passed
- _Year 3_
- **text:** German pages added
- _Year 3_
- **text:** Backups moved to a new server
- _Year 3_
- **text:** Security update tested on preview
- **status:** Updates are tested on the preview first, then go live.
## modern, proven tools.
_WHAT WE BUILD WITH_
We work with widely used tools that have open documentation. If you ever want to continue with another team, the code will feel familiar.
- **count:** {count} tools
- **Design and interface**
Design happens in Figma; the interface is built with Next.js, React and TypeScript. Tailwind CSS carries the design variables into code.
- **Content and data**
The content editor is Directus, open source and running on your own server. Form entries and custom data live in PostgreSQL and are read through Prisma.
- **Hosting and servers**
The site runs on Vercel or on a server you own at DigitalOcean. Server setups use Node.js, Docker and Nginx; Cloudflare can be added as a speed and security layer.
- **Analytics and email**
Visitor analytics run on Google Analytics, and form notifications are sent with Resend.
**Deploy path**
- **Vercel**
When code is pushed to the repository, the site redeploys on its own. No server maintenance needed.
1. Repository
2. Next.js
3. Vercel
4. Visitor
- **DigitalOcean**
The site is packaged with Docker and runs behind Nginx on a server you own. You choose the region where the data is kept.
1. Repository
2. Docker
3. Nginx
4. DigitalOcean
5. Visitor
> Logos are listed only to show the tools we use; this does not imply a partnership.
- **Figma:** Design and prototyping
- **Next.js:** Site framework
- **React:** Interface
- **TypeScript:** Type-safe code
- **Tailwind CSS:** Design system
- **Directus:** Content editor
- **PostgreSQL:** Database
- **Prisma:** Data access
- **Node.js:** Runtime
- **Vercel:** Managed hosting
- **DigitalOcean:** Servers
- **Docker:** Containers
- **NGINX:** Traffic routing
- **Cloudflare:** Speed and security
- **Google Analytics:** Analytics
- **Resend:** Form emails
_Interface labels:_ All tools
## four steps, clear timeline.
_PROCESS_
At the end of each step, you know what you approved and what was delivered.
1. **Discovery** · _Week 1_
Goals, audience, content and sitemap. We agree on scope and timeline together.
- **Delivered:** Sitemap and timeline
2. **Design** · _Weeks 2–3_
Phone and desktop designs, approved on a clickable prototype.
- **Delivered:** Approved prototype
3. **Build** · _Weeks 3–4_
Pages, languages, forms and the content editor. A working preview every week.
- **Delivered:** Preview site
4. **Launch** · _Week 5_
Speed tests, redirects from old URLs, team training and go-live.
- **Delivered:** Live site and training
_Representative interface data_ · Representative
> Representative
- Home
- Projects
- Office
- Publications
- Contact
- Phone
- Desktop
- **approved:** Approved
- **previewLabel:** Preview
- Home and projects
- Content editor connected
- English pages
- Speed test
- Redirects
- Team training
- Final check
> Live
> After launch: security monitoring, performance checks and support for new pages.
_Interface labels:_ Week {week}
## before we start.
_FAQ_
The questions we hear most before a decision. If yours isn't here, write to us directly.
> **Let's look at your site**
>
> No commitment, a short call
>
> Tell us about your current site and what you find missing. Your questions are answered by the people who will design and build the site.
> - [Send an email](mailto:info@oxarus.com) → `contact()`
**Question:** How long does it take to launch a corporate site?
**Answer:** Most projects take 3 to 5 weeks, depending on page count and specific needs. We give you a clear timeline up front and share a working preview every week.
**Question:** Can we update the content ourselves?
**Answer:** Yes. You change news, announcements, job posts, images and page copy in the editor without touching code. We give your team a short training session before launch.
**Question:** What happens to our current Google rankings?
**Answer:** We crawl every URL on your old site and redirect each one to its new page, so the rankings you've earned are preserved.
**Question:** Who owns the code and design files?
**Answer:** When the project ends, the source code, design files and intellectual property are transferred to your company. No annual theme licenses, no agency lock-in.
**Question:** How will it look on phones?
**Answer:** We start the design on phones. The site is tested separately on phones, tablets and a range of screen sizes.
**Question:** Where will the site be hosted?
**Answer:** We offer two options: managed hosting on Vercel or a server you own at DigitalOcean. The first needs no server maintenance; with the second, you choose the region where your data is kept. Your domain and email accounts stay where they are.
**Question:** Do you offer support after launch?
**Answer:** Yes. We provide ongoing support for security monitoring, server monitoring, performance checks and new pages.
## what grows with your site.
_OTHER SOLUTIONS_
- **AI search**
Get named in the answer when customers ask ChatGPT and Gemini.
- [AI search](https://oxarus.com/en/hub/ai-search)
- **E-commerce**
An online store built for your brand, a dealer portal and migration from off-the-shelf platforms.
- [E-commerce](https://oxarus.com/en/hub/ecommerce)
- **Custom systems**
A dashboard built for your company, for work that runs on Excel and WhatsApp.
- [Custom systems](https://oxarus.com/en/hub/custom-systems)
_Interface labels:_ Explore
## let's plan your new site.
_LET'S START_
No preparation needed. These three things are enough:
- Your current site's address (if you have one)
- A few sites you like
- Your target launch date
- [Get in touch](mailto:info@oxarus.com) → `contact()`
_Interface labels:_ Copied
## Actions
- [Start your project](https://oxarus.com/en/hub/corporate-web#contact-vault) → `open_page(path="/hub/corporate-web", anchor="contact-vault")`
- [What we deliver](https://oxarus.com/en/hub/corporate-web#services-grid) → `open_page(path="/hub/corporate-web", anchor="services-grid")`
- [Try the design system](https://oxarus.com/en/hub/corporate-web#design-heading) → `open_page(path="/hub/corporate-web", anchor="design-heading")`
- [Try the editor](https://oxarus.com/en/hub/corporate-web#editor-heading) → `open_page(path="/hub/corporate-web", anchor="editor-heading")`
- [See the page tree](https://oxarus.com/en/hub/corporate-web#languages-heading) → `open_page(path="/hub/corporate-web", anchor="languages-heading")`
- [See the measurements](https://oxarus.com/en/hub/corporate-web#quality-heading) → `open_page(path="/hub/corporate-web", anchor="quality-heading")`
- [Compare year by year](https://oxarus.com/en/hub/corporate-web#ledger-heading) → `open_page(path="/hub/corporate-web", anchor="ledger-heading")`
- [Send an email](mailto:info@oxarus.com) → `contact()`
- [Türkçe](https://oxarus.com/tr/hub/corporate-web) → `switch_locale(locale="tr", path="/hub/corporate-web")`
## Related pages
- [Oxarus Hub](https://oxarus.com/en/hub)
---
title: "Get visible in AI search"
description: "Your customers ask ChatGPT, Gemini and Perplexity. We get your site and listings ready to be recommended in those answers and track it monthly."
url: https://oxarus.com/en/hub/ai-search
key: hub-ai-search
route: /hub/ai-search
unit: hub
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/hub/ai-search
en: https://oxarus.com/en/hub/ai-search
documents:
json: https://oxarus.com/machine/en/hub/ai-search.json
jsonld: https://oxarus.com/machine/en/hub/ai-search.jsonld
txt: https://oxarus.com/machine/en/hub/ai-search.txt
schema: oxarus.machine/2.0
---
# Get visible in AI search
> Your customers ask ChatGPT, Gemini and Perplexity. We get your site and listings ready to be recommended in those answers and track it monthly.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Hub](https://oxarus.com/en/hub) › [AI Search](https://oxarus.com/en/hub/ai-search)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [your customers no longer search google. they ask ai instead. are you in the answer?](#hero)
- [three names, none of them you.](#problem)
- [wherever they ask.](#engines)
- [it decides from six sources.](#signals)
- [ranked on google, recommended by ai.](#compare)
- [get visible in three steps.](#process)
- [what the monthly report shows.](#case)
- [on your mind.](#faq)
- [what does ai say about you?](#cta)
## your customers no longer search google. they ask ai instead. are you in the answer?
_HUB · AI VISIBILITY_
- **engines:** On ChatGPT, Gemini, Perplexity and more
- [Get in touch](https://oxarus.com/en/hub/ai-search#cta-heading) → `open_page(path="/hub/ai-search", anchor="cta-heading")`
- [How it works](https://oxarus.com/en/hub/ai-search#process-heading) → `open_page(path="/hub/ai-search", anchor="process-heading")`
_Representative interface data_
**Can you recommend a good dental clinic in Kadıköy?**
> Representative
- **searchLabel:** Search
- **Search:** dentist kadıköy
- **results:** 10 blue links
- **askLabel:** Assistant
- **answerLabel:** Answer
- Moda Dental Care
- Bahariye Dental
- Kalamış Dental Studio
- **you:** You?
## three names, none of them you.
_THE PROBLEM_
Many people looking for a business no longer scroll through search results. They ask ChatGPT or Gemini and call one of the few names it suggests. If your information is scattered or incomplete, your name isn't one of them.
_Representative interface data_ · Sample answer. Clinic names are illustrative.
- **question:** Can you recommend a good dental clinic in Kadıköy?
- **Question**
The customer asks for what they need in their own words.
- **Sources**
The assistant reads your site, your Google profile, reviews and directories.
- **Answer**
It suggests a few names. A business that isn't listed doesn't get the call.
_Representative interface data_ · Sample answer. Clinic names are illustrative.
> Representative answers
- **assistantsLabel:** Assistants
- **before:** Today
> After the fixes
- **replay:** Replay answer
- **reading:** Reading sources
- **Your business:** Smile Atelier Dental
- **missing:** Not in the answer
- **rank:** Ranked {rank}
- **introBefore:** Three clinics with strong reviews stand out in Kadıköy:
- **introAfter:** Three clinics stand out in Kadıköy:
- **Smile Atelier Dental**
- **detail:** implants and clear aligners, open Saturdays
- **Moda Dental Care**
- **detail:** implants and cosmetic dentistry
- **Bahariye Dental**
- **detail:** pediatric dentistry, open on weekends
- **Kalamış Dental Studio**
- **detail:** clear aligners and orthodontics
**Sources**
- **Smile Atelier Dental**
- **page:** Services page
- **Smile Atelier Dental**
- **page:** Google Business Profile
- **Moda Dental Care**
- **page:** Website
- **Bahariye Dental**
- **page:** Google Business Profile
- **Kalamış Dental Studio**
- **page:** Dentist directory
- **Dental clinics in Kadıköy**
- **page:** Local news roundup
## wherever they ask.
_PLATFORMS_
Your customers don't ask just one app. They ask the assistant on their phone, the search engine's summary or the AI inside WhatsApp. We make sure every one of them reads the same information.
- **Chat apps**
They type the question and compare the suggested names on one screen.
- **Search summaries**
They search Google or Bing and read the ready-made summary above the results.
- **Phone assistants**
They ask out loud and hear a single answer.
- **Messaging apps**
They message the AI inside WhatsApp or Instagram.
- **ChatGPT:** OpenAI
- **Gemini:** Google
- **Perplexity:** Perplexity AI
- **Claude:** Anthropic
- **AI Overviews:** Google Search
- **Meta AI:** WhatsApp · Instagram
- **Copilot:** Microsoft
- **Apple Intelligence:** Siri
- **DeepSeek:** DeepSeek
- **Le Chat:** Mistral AI
## it decides from six sources.
_WHAT AI LOOKS AT_
An AI doesn't decide whether to recommend you by looking at a single page. It gathers everything about you online and cross-checks it. We fix each of these six sources, one by one.
- **Your website** · _WEBSITE_
What you do, where you are and who you serve should be spelled out on your site. AI doesn't guess; it reads what's written.
- Clear, dedicated service pages
- Address, phone and opening hours
- Behind-the-scenes tags that AI reads
- **Your Google Business Profile** · _MAPS_
The most-checked source for local questions. A missing category, outdated hours or a wrong address can drop you off the list.
- Correct categories and service list
- Up-to-date photos and hours
- Regular posts and updates
- **Customer reviews** · _REVIEWS_
AI looks at both the number and the content of reviews. Reviews that say "great for implants" put you forward on implant questions.
- A routine for requesting reviews
- Timely replies to reviews
- Balance across platforms
- **Industry directories** · _DIRECTORIES_
Your listings in doctor, lawyer, restaurant and tradesperson directories. The name, address and phone should be identical everywhere.
- Identifying the directories that matter
- Fixing inconsistent listings
- Creating missing listings
- **What's written about you** · _MENTIONS_
Local news, blogs, forums and lists. When others mention you, it shows AI that you're a real, known business.
- A map of existing mentions
- Content opportunities with local publications
- Correcting inaccurate information
- **Content ready for questions** · _ANSWERS_
Your customers ask "how long does it take", "how much is it" and "does it hurt". If your site answers these, AI takes the answer from you.
- A list of real customer questions
- Short, clear answer pages
- An FAQ section
_Representative interface data_
**Business record**
- **subtitle:** What six sources add up to
> Representative
- **before:** Today
> After the fixes
- **record:** Record
- **code:** Structured data
- **consistent:** Consistent
- **conflict:** Conflicting
- **missing:** Missing
- **conflicts:** Conflicts: {count}
- **gaps:** Missing: {count}
- **reported:** What this source says
- **noData:** No structured data on the site
- Type too generic
- No opening hours
- No services
- **codeFixed:** Same details as the site, Google profile and directories
- **Business name**
- **value:** Smile Atelier Dental
- **Category**
- **value:** Dental clinic
- **Location**
- **value:** Moda, Kadıköy
- **Saturday**
- **value:** 10:00–16:00
- **Services**
- **value:** Implants, clear aligners
- **services:** General dentistry
- **category:** Health center
- **hours:** Closed
- **brand:** Smile Atelier Oral and Dental Health Clinic
- **area:** Bostancı
## ranked on google, recommended by ai.
_SEO AND AI_
If you already do SEO, that work isn't wasted; AI visibility builds on top of it. But the two have different goals and different measures.
| | CLASSIC SEO | AI VISIBILITY |
| --- | --- | --- |
| What does the customer see? | Ten blue links: They scan the list, click a few sites and do the comparing themselves. | One answer and a few names: They get a ready-made answer that has already done the comparing. If you're not on the list, there's nothing to click. |
| What's the goal? | Ranking high on page one: Raising your ranking for specific keywords. | Your name in the answer: Being one of the recommended names across the different questions customers might ask. |
| What gets evaluated? | Mostly your site itself: Page content, speed and links pointing to your site. | Your entire footprint online: How consistent your site, Google profile, reviews, directories and mentions are with each other. |
| How is it measured? | Ranking and click reports: Google Search Console and rank-tracking tools. | Asking and logging questions regularly: Every month we ask the same questions to different AI tools and report whether you're recommended. |
_Representative interface data_
**Can you recommend a good dental clinic in Kadıköy?**
> Representative
- **searchTitle:** Search results
- **answerTitle:** AI answer
- **query:** dentist kadıköy
- **you:** You
- **rank:** Rank
- **The 10 best dental clinics in Kadıköy**
- **source:** Local guide
- **Implants and cosmetic dentistry**
- **source:** Moda Dental Care
- **Pediatric dentistry, open on weekends**
- **source:** Bahariye Dental
- **Implants and clear aligners**
- **source:** Smile Atelier Dental
- **Clear aligners and orthodontics**
- **source:** Kalamış Dental Studio
- **intro:** Three clinics stand out in Kadıköy:
- Smile Atelier Dental
- Moda Dental Care
- Bahariye Dental
- **footprint:** Sources read
- Website
- Google profile
- Reviews
- Directories
- News
- **log:** Monthly question log
- Dental clinic in Kadıköy
- Dentist open on weekends
- Clear aligner clinic
## get visible in three steps.
_HOW WE WORK_
First we measure, then we fix, then we track every month.
1. **We audit** · _WEEK 1_
We ask ChatGPT, Gemini and Perplexity the questions your customers might ask. Do they recommend you, what do they say about you, and why do they pick your competitors? You see all of it in a single report.
**What you get**
- Visibility report: the questions where you're recommended
- A summary of why competitors get picked
- A prioritized task list
2. **We fix** · _WEEKS 2–6_
We make your site, Google Business Profile and industry directory listings easy for AI to read correctly. Your address, services, opening hours and specialties become consistent and clear everywhere.
**What you get**
- Site copy and behind-the-scenes tags
- Google profile and directory listings fixed
- Pages that answer customer questions
3. **We track** · _MONTHLY_
Every month we ask the same questions again and send you a short report on what changed. If something slips, we find the cause and fix it.
**What you get**
- A short monthly report
- Cause and fix if anything slips
- New questions and opportunities
_Representative interface data_
> Representative
- **audit:** 4 questions, 4 assistants
- **fix:** Source fixes
- **track:** Answers that name you
_Interface labels:_ STEP
## what the monthly report shows.
_REPRESENTATIVE REPORT_
Four questions, four assistants and three months for a representative dental clinic.
_Representative interface data_ · Representative example, not a real client result. Timing and results differ for every business.
**Start**
- **value:** 0 / 4
- **body:** Not recommended for any of the four questions.
_Representative interface data_ · Representative example, not a real client result. Timing and results differ for every business.
**Month 3**
- **value:** 3 / 4
- **body:** Most assistants recommend the clinic for three of the same four questions.
| 4 questions asked | Month 3 |
| --- | --- |
| A good dental clinic in Kadıköy? | ✓ |
| Where should I go for implants in Istanbul? | ✓ |
| Can you recommend a dentist open on weekends? | – |
| A clear aligner clinic on the Asian side? | ✓ |
_Representative interface data_ · Representative example, not a real client result. Timing and results differ for every business.
- Start
- Month 1
- Month 2
- Month 3
- **cells:** Recommended in {count} of 16 answers
- **recommended:** Recommended
- **not recommended:** Not recommended
A question counts once at least two of the four assistants recommend the clinic.
## on your mind.
_FAQ_
If your question isn't here, write to us.
**Question:** How is this different from SEO?
**Answer:** SEO is about where you rank on Google. Here, the goal is for your name to appear in the answer when someone asks AI a question. The two share the same foundation; if you already have SEO work in place, we build on top of it.
**Question:** How soon will we see results?
**Answer:** The first changes usually show within a few weeks. For most businesses, earning a lasting spot takes around three months.
**Question:** Can you promise we'll be recommended?
**Answer:** No. Nobody decides what an AI will answer. We make sure the information about you is accurate, consistent and easy to find, and we measure and share the results every month.
**Question:** Will it work for my industry?
**Answer:** If customers find you by asking a question, yes: clinics, lawyers, restaurants, tradespeople, schools, local shops. If you're not sure, write to us and we'll ask a few questions on your behalf and take a look.
**Question:** Do I need to rebuild my website?
**Answer:** Usually not. We work on your existing site by adding copy, pages and behind-the-scenes tags. If the site is too old or can't be edited, we'll say so clearly in the first report.
**Question:** Which AI tools do you track?
**Answer:** ChatGPT, Gemini, Perplexity, Microsoft Copilot and Google's AI Overviews. If another tool matters in your industry, we add it to the list.
**Question:** How much of my time does it take?
**Answer:** A one-hour call at the start and a check of your business details. After that, you just read one report a month; we do the work.
> **Let's take a look first**
>
> No commitment, just a quick check
>
> Send us your business name and city. We'll ask AI tools a few questions your customers might ask and tell you what we find.
> - [Request a check](mailto:info@oxarus.com) → `contact()`
## what does ai say about you?
_FREE FIRST LOOK_
Just tell us your business name and the city you're in.
- [Get in touch](mailto:info@oxarus.com) → `contact()`
_Interface labels:_ Copied
## Actions
- [Get in touch](https://oxarus.com/en/hub/ai-search#cta-heading) → `open_page(path="/hub/ai-search", anchor="cta-heading")`
- [How it works](https://oxarus.com/en/hub/ai-search#process-heading) → `open_page(path="/hub/ai-search", anchor="process-heading")`
- [Request a check](mailto:info@oxarus.com) → `contact()`
- [Türkçe](https://oxarus.com/tr/hub/ai-search) → `switch_locale(locale="tr", path="/hub/ai-search")`
## Related pages
- [Oxarus Hub](https://oxarus.com/en/hub)
---
title: "E-commerce stores and B2B dealer portals"
description: "Custom online stores, B2B dealer portals and migration off hosted platforms. iyzico, shipping, Trendyol, Hepsiburada and ERP integrations ready at handover."
url: https://oxarus.com/en/hub/ecommerce
key: hub-ecommerce
route: /hub/ecommerce
unit: hub
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/hub/ecommerce
en: https://oxarus.com/en/hub/ecommerce
documents:
json: https://oxarus.com/machine/en/hub/ecommerce.json
jsonld: https://oxarus.com/machine/en/hub/ecommerce.jsonld
txt: https://oxarus.com/machine/en/hub/ecommerce.txt
schema: oxarus.machine/2.0
---
# E-commerce stores and B2B dealer portals
> Custom online stores, B2B dealer portals and migration off hosted platforms. iyzico, shipping, Trendyol, Hepsiburada and ERP integrations ready at handover.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Hub](https://oxarus.com/en/hub) › [E-Commerce](https://oxarus.com/en/hub/ecommerce)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [a store that sells.](#hero)
- [three starting points.](#audiences)
- [three steps from cart to confirmation.](#checkout)
- [every order in one list.](#operations)
- [every dealer sees their own prices.](#dealer)
- [connects to the services you use.](#logos)
- [a hosted platform or your own store?](#compare)
- [switch without losing a thing.](#migration)
- [live in four steps.](#process)
- [your questions.](#faq)
- [let's talk shop.](#cta)
## a store that sells.
_HUB · E-COMMERCE_
Customers who find your product should be able to check out in three steps. We build your store from scratch and hand it over with payments, shipping, marketplaces and accounting already connected.
- [Get in touch](https://oxarus.com/en/hub/ecommerce#cta-heading) → `open_page(path="/hub/ecommerce", anchor="cta-heading")`
- [What we build](https://oxarus.com/en/hub/ecommerce#checkout-heading) → `open_page(path="/hub/ecommerce", anchor="checkout-heading")`
- No monthly platform license
- You own the code
- Migration from your current store
1. Product
2. Cart
3. Order
_Representative interface data_ · Illustrative store interface.
- **storeName:** dune atelier
- **tabTitle:** {page} · dune atelier
- **home:** Bestsellers
- **product:** Stone mug
- **checkout:** Secure checkout
- **Done:** Order confirmed
- **announcement:** Free shipping on orders over {amount} · Free 14-day returns
New arrivals · Bestsellers · Mugs · Tableware · Our story
- **search:** Search products
- Home
- Bestsellers
- **homeCount:** {count} products
- **sort:** Sort: Featured
- **filters:** Filter
- **clearFilters:** Clear
- **categoryLabel:** Category
- Mugs
- Tableware
- Textiles
- **priceLabel:** Price
- **inStockOnly:** In stock only
**{discount} off stone mugs**
- **eyebrow:** Autumn edit
- **cta:** Shop mugs
- **Stone mug**
- **Stone mug**
- **Linen napkin set**
- **Serving plate**
- **bestseller:** Bestseller
- **lowStock:** Only {count} left
- **quickAdd:** Quick add
- Home
- Mugs
- Stone mug
- **product:** Stone mug
- **productMeta:** Handmade ceramic · 350 ml · Dishwasher safe
- **reviews:** {count} reviews
- **installment:** {count} installments of {amount} · No extra charge
- **colorLabel:** Color
- Sand
- Charcoal
- Mist
- **inStock:** In stock · ships tomorrow
- **soldOut:** Sold out · we'll let you know
- **soldOutBadge:** Sold out
- **qtyLabel:** Qty
- **addToCart:** Add to cart
- **added:** Added to cart
- **notify:** Notify me
- Ships tomorrow
- Free 14-day returns
- Secure checkout
**Your cart**
- **Stone mug**
- **Linen napkin set**
- **itemCount:** {count} items
- **freeShipping:** You've unlocked free shipping
- **freeShippingFrom:** Over {amount}
- **upsellLabel:** Goes well with
- **Goes well with:** Add
- **coupon:** Discount code
- **subtotal:** Subtotal
- **Delivery:** Shipping
- **free:** Free
- **total:** Total
- **vatIncluded:** VAT included
- **checkoutCta:** Checkout
- Cart
- Delivery
- Payment
- **secure:** Secure checkout
- **addressLabel:** Deliver to
- **Deliver to:** Elif Yıldız
- **Deliver to:** Moda, Kadıköy · Istanbul
- **Delivery:** Standard · Aras Kargo · 2–3 business days
- **edit:** Change
- **paymentLabel:** Payment
- **Installments:** Pay in full or in installments.
- Card
- Bank transfer
- Cash on delivery
- **cardNumber:** Card number
- **expiry:** Expiry
- **cvc:** CVC
- **single:** Pay in full
- **installmentCount:** {count} installments
- **perMonth:** {amount} a month
- **consent:** I accept the pre-contract information and the distance sales agreement.
- **pay:** Pay with 3D Secure
- **paying:** Your bank is verifying
**Thank you, Elif!**
- **order:** Order no. {number}
- **body:** A confirmation email and text are on their way. We'll send the tracking number as soon as the parcel ships.
- **nextTitle:** What happens on its own after the order
1. **Payment approved** · _iyzico · 3D Secure_
2. **e-Archive invoice issued** · _Paraşüt_
3. **Shipping label ready** · _Aras Kargo · ships tomorrow_
4. **Stock updated** · _Site, Trendyol, Hepsiburada and Amazon_
- **pending:** Queued
**Create your account in one step**
- **body:** Follow your orders and returns in one place.
- **cta:** Set a password
- **summary:** Order summary
- **paidWith:** Card · Paid in full
- **eta:** Estimated delivery
- **etaValue:** 2–3 business days
**Track your order**
- **code:** Aras Kargo · 7184 2290 13
1. Placed
2. Preparing
3. Shipped
4. Delivered
- **cta:** Track
- **todayLabel:** Today's revenue
- **ordersLabel:** {count} orders
- **tag:** Representative
- **Marketplace order**
- **text:** {order} · Hepsiburada
- **Price sync**
- **text:** Same price on 4 channels
- **Cart**
- **text:** {count} items · free shipping
- **Payment**
- **text:** Waiting for 3D Secure
- **New order**
- **text:** {order} · Site · Kadıköy
- **Stock updated**
- **text:** Stone mug, Sand · {from} → {to}
## three starting points.
_WHICH ONE ARE YOU_
Not every business starts e-commerce from the same place. Pick your situation and see how we'd approach it.
- **Your first real online store** · _Business with a shop_
“Your shop or Instagram account sells, but orders live in DMs, payments arrive by bank transfer and stock is tracked in a notebook.”
We move your products, photos and prices into a well-organized store. Card payments, shipping labels and order notifications work from day one.
- Bulk product upload
- Card, bank transfer and cash on delivery
- Order alerts on WhatsApp
- Training on the admin panel
- [See the checkout flow](https://oxarus.com/en/hub/ecommerce#checkout-heading) → `open_page(path="/hub/ecommerce", anchor="checkout-heading")`
- **Your own stack, without limits** · _Growing online brand_
“You sell on a hosted platform, but pages are slow, commissions and app fees climb as you grow, and you can't add the features you need.”
We move your store onto code written for you. Products, customers and order history come across intact, and we redirect old URLs to new ones to protect your Google rankings.
- Migration from Shopify, ikas, Ticimax, WooCommerce
- Fast-loading product and category pages
- Campaigns and bundles built around you
- No monthly platform license
- [See the migration plan](https://oxarus.com/en/hub/ecommerce#migration-heading) → `open_page(path="/hub/ecommerce", anchor="migration-heading")`
- **An ordering portal for your dealers** · _Manufacturer or wholesaler_
“Your dealers order by phone and email, each on different prices and payment terms, and someone keys it all into the ERP by hand.”
Each dealer sees their own price list, balance and order history. Orders flow into Logo, Mikro or Netsis automatically.
- Dealer-specific pricing and discounts
- Account balance and payment terms
- Bulk and repeat orders
- Two-way ERP integration
- [See the dealer portal](https://oxarus.com/en/hub/ecommerce#dealer-heading) → `open_page(path="/hub/ecommerce", anchor="dealer-heading")`
_Interface labels:_ Today · What we build
## three steps from cart to confirmation.
_STOREFRONT, SHIPPING AND PAYMENT_
Customers confirm their cart without creating an account, pick a delivery option and pay by card, bank transfer or cash on delivery. Try the flow step by step below.
- **A store made for you** · _STOREFRONT_
No templates. Product, category and campaign pages designed around your brand and fast on mobile.
- Product filters and search
- Campaign and coupon logic
- Easy-to-edit content pages
- **Shipping and returns** · _SHIPPING_
Once an order is confirmed, the shipping label is created and the tracking number goes to the customer. Returns are handled from the dashboard.
- Yurtiçi, Aras, MNG integration
- Automatic tracking notifications
- Returns and exchange flow
- **Payments and installments** · _PAYMENTS_
Card, installments, bank transfer or cash on delivery. Checkout stays short, and customers can buy without creating an account.
- iyzico and PayTR
- 3D Secure and installment table
- Fast guest checkout
_Representative interface data_ · Representative
**Checkout flow**
> Representative
- **storeName:** dune atelier
1. Cart
2. Delivery
3. Payment
- **Stone mug**
- **Linen napkin set**
- **decrease:** Remove one
- **increase:** Add one
- **freeShippingLeft:** {amount} away from free shipping
- **freeShippingDone:** You've unlocked free shipping
- **coupon:** Discount code
- **couponCode:** DUNE10
- **couponApply:** Apply
- **couponRemove:** Remove
- **couponApplied:** 10% off your first order
- **guest:** Continue as guest
- **addressLabel:** Delivery address
- **Delivery address:** Elif Yıldız
- **Delivery address:** Moda, Kadıköy · Istanbul
**Delivery option**
- **Standard delivery** · _2–3 business days_
- **carrier:** Aras Kargo
- **Next-day delivery** · _At your door tomorrow_
- **carrier:** Yurtiçi Kargo
- **paymentLabel:** Payment method
- **card:** Card
- **transfer:** Bank transfer
- **cod:** Cash on delivery
- **cardNumber:** Card number
- **cardHolder:** Cardholder
- **installmentsLabel:** Installments
- **single:** Pay in full
- **installment:** {count} installments
- **perMonth:** {amount} a month
- **noFee:** No extra charge
- **withFee:** Includes installment fee
> 3% off for bank transfers. The order is confirmed once the payment arrives.
> Paid in cash or by card on delivery; a service fee is added to the total.
- **continue:** Continue
- **back:** Back
- **payCard:** Pay with 3D Secure
- **placeOrder:** Place order
- **summary:** Order summary
- **subtotal:** Subtotal
- **discount:** Discount
- **Delivery option:** Shipping
- **free:** Free
- **transferDiscount:** Transfer discount
- **codFee:** Cash on delivery fee
- **installmentFee:** Installment fee
- **total:** Total
**Thank you, Elif!**
- **order:** Order no. 10482
- **body:** A confirmation email and text message are on their way.
**What happens on its own after the order**
- **paid:** Payment approved
- **paidMeta:** iyzico · 3D Secure
- **transfer:** Waiting for the transfer
- **transferMeta:** The order is confirmed once it arrives
- **cod:** To be collected on delivery
- **codMeta:** The courier collects at the door
- **invoice:** e-Archive invoice issued
- **invoiceMeta:** Paraşüt
- **labelReady:** Shipping label ready
- **stock:** Stock updated
- **stockMeta:** Trendyol and Hepsiburada
- **restart:** Start over
- Secure checkout
- Free 14-day returns
- Ships tomorrow
## every order in one list.
_MARKETPLACES AND ACCOUNTING_
Orders from your site, Trendyol, Hepsiburada and Amazon land in the same dashboard. When a product sells, its stock drops on every channel, the invoice is issued and the order goes to your accounting software.
- **Marketplace sync** · _MARKETPLACES_
Your products, prices and stock on Trendyol, Hepsiburada and Amazon stay in sync with your store.
- Stock and pricing from one dashboard
- Marketplace orders in one place
- No overselling
- **ERP and e-invoicing** · _ACCOUNTING_
Orders flow into your accounting software and get invoiced. Manual data entry goes away.
- Logo, Mikro, Netsis integration
- e-Archive and e-Invoice
- Paraşüt integration
_Representative interface data_ · Representative
**Admin panel**
- **storeName:** dune atelier
> Representative
- **simulate:** New order
- **reset:** Reset
- **revenue:** Today's revenue
- **Orders:** Orders
- **invoiced:** Invoices issued
- **lowStock:** Low stock
- **all:** All
- **site:** Site
- **trendyol:** Trendyol
- **hepsiburada:** Hepsiburada
- **amazon:** Amazon
- **order:** Order
- **product:** Product
- **amount:** Amount
- **status:** Status
- **paid:** Paid
- **invoiced:** Invoiced
- **shipped:** Shipped
- **emptyFilter:** No orders from this channel yet.
**Stock**
> One stock, four channels
- **Stone mug**
- **Stone mug**
- **Linen napkin set**
- **Serving plate**
- **low:** Running low
- **out:** Sold out
- **lowAlert:** {product} is down to {count}.
- **outAlert:** {product} sold out and was taken off sale on every channel.
- **dismiss:** Dismiss alert
- **synced:** Same on every channel
**Accounting export**
- **invoice:** e-Archive invoice
- **erp:** Sent to Logo
- **empty:** Waiting for a new order.
- Ankara
- Izmir
- Bursa
- Antalya
- Eskişehir
- Kayseri
- Trabzon
- Konya
## every dealer sees their own prices.
_B2B DEALER PORTAL_
Your dealers order through the portal instead of by phone or email. Price list, discount, payment terms and credit limit are set per dealer, and orders flow into your ERP automatically.
**Dealer portal**
_B2B_
Dealers order from their own accounts at their own prices. Approvals, payment terms and credit limits work exactly the way you set them.
- Dealer-specific price lists
- Account balance and credit limit
- Bulk and repeat orders
_Representative interface data_ · Representative
**Dealer portal**
- **storeName:** dune atelier
> Representative
**Pick a dealer**
- **Kivrel**
- **sector:** Furniture store
- **tier:** Gold dealer
- **terms:** 60-day terms
- **Moravi**
- **sector:** Coffee roaster
- **tier:** Silver dealer
- **terms:** 30-day terms
- **Olvesta**
- **sector:** Boutique hotel
- **tier:** Standard dealer
- **terms:** Payment upfront
- **priceList:** Price list
- **vatExcluded:** Excl. VAT
- **product:** Product
- **yours:** Your price
- **qty:** Cases
- **total:** Amount
- **Stone mug**
- **size:** 350 ml
- **Espresso cup**
- **size:** 90 ml
- **Serving plate**
- **size:** 27 cm
- **Bowl**
- **size:** 16 cm
- **pack:** {count} per case
- **discount:** {percent} off
- **decrease:** Remove one case
- **increase:** Add one case
- **limitLabel:** Account
- **Account:** Open balance
- **Account:** Available credit
- **Account:** With this order
- **withinLimit:** Within the limit, processed without approval.
- **overLimit:** Over the limit, the order goes for approval.
- **subtotal:** Subtotal
- **vat:** VAT
- **total:** Grand total
- **reorder:** Repeat last order
- **clear:** Clear
- **submit:** Send order
**Order received**
- **body:** Sent to Logo.
- **approval:** Sent to a manager for approval.
- **newOrder:** New order
- **empty:** Choose the number of cases.
## connects to the services you use.
_READY INTEGRATIONS_
We connect payment, shipping, marketplace, accounting and analytics services to your store. If you have a contract with a provider that isn't listed, we can connect that too.
- **count:** {count} services
- **Payments**
Cards, wallets and installments. Refunds and cancellations are handled from the dashboard.
- **Shipping**
Once an order is confirmed, the label is created and the tracking number goes to the customer.
- **Sales channels**
Products, prices and stock go out to each channel; orders come back into one list.
- **Accounting**
e-Archive and e-Invoices are issued, and orders go to your ERP.
- **Alerts and analytics**
New orders show up on WhatsApp, and sales show up in your analytics.
> Brands are listed only to show which services can be connected; this does not imply a partnership.
- **Payments:** iyzico, PayTR
- **Cards:** Visa, Mastercard
- **Wallets:** Apple Pay, Google Pay
- **Shipping:** Yurtiçi Kargo, Aras Kargo, MNG Kargo
- **Marketplaces:** Trendyol, Hepsiburada, Amazon
- **Product listings:** Google Shopping
- **Social selling:** Instagram
- **Order alerts:** WhatsApp
- **Analytics:** Google Analytics
- **ERP:** Logo, Mikro, Netsis
- **E-invoicing:** Paraşüt
_Interface labels:_ All
## a hosted platform or your own store?
_HOSTED PLATFORM VS. CUSTOM BUILD_
Hosted platforms are a good place to start. But as sales grow, so do the monthly fees, commissions and limits.
| | HOSTED PLATFORM | BUILT FOR YOUR BRAND |
| --- | --- | --- |
| What do you pay every month? | Plan fees and app subscriptions: As sales grow you move up a plan, and every extra feature means another app. | No license fees: Built once. Your only monthly costs are hosting and whatever support you choose. |
| Who owns the code and data? | The platform: When you leave the platform, your design and most of your features stay behind. | You do: Source code, design and all customer data are yours, and the store runs on your servers. You can continue with any team you like. |
| What if you need something custom? | Only what the platform allows: Dealer pricing, bundles or custom campaigns are often only half-solved with plugins. | Built for your needs: The store follows your business rules, not the limits of a single plugin. |
| How fast are the pages? | Themes and apps slow it down: Every app adds more code to the page, and load times on mobile grow. | Only the code it needs: Pages ship only the code they need, so they load fast on mobile, and search engines reward that. |
_Representative interface data_ · Representative
> Representative
**Monthly line items**
**HOSTED PLATFORM**
- Platform plan
- Theme license
- Filter app
- Reviews app
- Wholesale plugin
- Platform transaction fee
**BUILT FOR YOUR BRAND**
- Hosting
- Maintenance, optional
**What you keep when you leave**
- **keeps:** Comes with you
- **leaves:** Stays on the platform
**HOSTED PLATFORM**
- Product list
- Customer list
**HOSTED PLATFORM**
- Theme and design
- App settings
- Custom logic
**BUILT FOR YOUR BRAND**
- Source code
- Database
- Design files
- Server access
**Dealer pricing rule**
**HOSTED PLATFORM**
- A single percentage discount
- Pricing by case quantity
- Payment terms and credit limit
- **BUILT FOR YOUR BRAND:** The rule is written around how you do business.
**Code loaded on a product page**
**HOSTED PLATFORM**
- Theme
- Reviews app
- Live chat
- Cross-sell
- Pop-up
- Tracking scripts
**BUILT FOR YOUR BRAND**
- Page
- Cart
- Analytics
## switch without losing a thing.
_STORE MIGRATION_
We move the products, customers, orders and Google rankings from your current store to the one we build for you. The store stays open on switchover night.
**From**
- Shopify
- ikas
- Ticimax
- WooCommerce
- IdeaSoft
- T-Soft
- **To:** A store built for your brand
> The code and data are yours; you're not tied to any platform.
_Representative interface data_ · Illustrative figures.
- **Products and variants**
- **detail:** With photos and descriptions
- **value:** 4,280
- **Customer accounts**
- **detail:** With a password reset flow
- **value:** 18,650
- **Past orders**
- **detail:** With invoice and shipping details
- **value:** 52,310
- **Redirected URLs**
- **detail:** From each old address to its new page
- **value:** 6,120
- **queued:** Queued
- **running:** Moving
- **verified:** Verified
**Switchover plan**
- **Preview store**
The new store running on your migrated data. You check it before launch.
- **Final sync**
Orders and customers that came in after the preview move over on switchover night.
- **Switchover**
At your lowest-traffic hour, visitors start landing on the new store.
- **Redirect check**
We test that old product and category addresses reach their new pages.
- **First weeks**
Payments, orders and Google rankings are watched closely.
- **open old:** Current store is selling
- **open new:** New store is selling
_Interface labels:_ Play the migration · Play again
## live in four steps.
_HOW WE WORK_
At the end of each step, you know exactly what's been delivered.
1. **Discovery** · _WEEKS 1–2_
We talk through your products, your customers and how you sell today, and work out together which integrations you need.
**What you get**
- Scope and integration list
- Sitemap
- Clear price and timeline
2. **Design** · _WEEKS 3–5_
We design the home, category, product, cart and checkout screens around your brand. Nothing gets coded without your approval.
**What you get**
- Desktop and mobile designs
- Clickable prototype
- Revision rounds
3. **Build** · _WEEKS 6–10_
We code the store and set up payment, shipping, marketplace and accounting integrations. If you're migrating, your data moves over at this stage.
**What you get**
- Preview store
- Working integrations
- Data migration report
4. **Launch** · _WEEK 10+_
We take the store live and watch the first weeks closely. Your team gets trained on the dashboard.
**What you get**
- Live store
- Dashboard training
- Maintenance and support options
_Representative interface data_ · Representative
> Representative
- **scope:** Integration list
- **screens:** Approved screens
- **tests:** Integration tests
- **launch:** First week, daily orders
- Home
- Category
- Product
- Cart
- Checkout
- Test payment
- Shipping label
- Stock sync
- e-Archive invoice
- **day:** Day {day}
_Interface labels:_ STEP
## your questions.
_FAQ_
Don't see your question here? Write to us.
**Question:** Is a custom store right for me, or a hosted platform?
**Answer:** If you're just starting out with a small catalog, a hosted platform may make more sense, and we'll tell you so. If sales are growing, you have custom business rules, or monthly costs are starting to hurt, a custom build is cheaper and more flexible in the long run.
**Question:** Will I be able to manage the store myself?
**Answer:** Yes. You manage products, prices, campaigns, orders and content pages from a dashboard that requires no technical knowledge. We train your team before launch.
**Question:** Will my sales stop during migration?
**Answer:** No. Your current store keeps selling until the new one is ready and tested. We switch over at your lowest-traffic hour.
**Question:** Will I lose my Google rankings?
**Answer:** We redirect every old product and category URL to its new address, and titles and descriptions come across too. The goal is for your rankings to be unaffected by the switch.
**Question:** Which payment and shipping providers do you work with?
**Answer:** For payments we often work with iyzico and PayTR; for shipping, Yurtiçi, Aras and MNG. If you have a contract with another provider, we can connect that too.
**Question:** How does stock stay in sync with Trendyol and Hepsiburada?
**Answer:** Stock and pricing are managed in one place. When a product sells on one channel, its stock drops everywhere else, so you never sell what you don't have.
**Question:** What happens after launch?
**Answer:** We watch the first weeks closely. After that, we can continue with monthly maintenance and development if you'd like; if not, the code is already yours.
> **Let's look at your store**
>
> No commitment, just a short call
>
> Tell us where you sell today and where you want to go. We'll tell you honestly which path fits, even if it's a hosted platform.
> - [Request a call](mailto:info@oxarus.com) → `contact()`
## let's talk shop.
_LET'S START_
Just tell us what you sell and where you sell it today.
- [Get in touch](mailto:info@oxarus.com) → `contact()`
_Interface labels:_ Copied
## Actions
- [Get in touch](https://oxarus.com/en/hub/ecommerce#cta-heading) → `open_page(path="/hub/ecommerce", anchor="cta-heading")`
- [What we build](https://oxarus.com/en/hub/ecommerce#checkout-heading) → `open_page(path="/hub/ecommerce", anchor="checkout-heading")`
- [See the migration plan](https://oxarus.com/en/hub/ecommerce#migration-heading) → `open_page(path="/hub/ecommerce", anchor="migration-heading")`
- [See the dealer portal](https://oxarus.com/en/hub/ecommerce#dealer-heading) → `open_page(path="/hub/ecommerce", anchor="dealer-heading")`
- [Request a call](mailto:info@oxarus.com) → `contact()`
- [Türkçe](https://oxarus.com/tr/hub/ecommerce) → `switch_locale(locale="tr", path="/hub/ecommerce")`
## Related pages
- [Oxarus Hub](https://oxarus.com/en/hub)
---
title: "Custom dashboards, CRM and operations systems"
description: "We move work that runs on Excel, WhatsApp and paper into a single dashboard. Orders, inventory, service, customers and staff, with no per-user fees."
url: https://oxarus.com/en/hub/custom-systems
key: hub-custom-systems
route: /hub/custom-systems
unit: hub
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/hub/custom-systems
en: https://oxarus.com/en/hub/custom-systems
documents:
json: https://oxarus.com/machine/en/hub/custom-systems.json
jsonld: https://oxarus.com/machine/en/hub/custom-systems.jsonld
txt: https://oxarus.com/machine/en/hub/custom-systems.txt
schema: oxarus.machine/2.0
---
# Custom dashboards, CRM and operations systems
> We move work that runs on Excel, WhatsApp and paper into a single dashboard. Orders, inventory, service, customers and staff, with no per-user fees.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Hub](https://oxarus.com/en/hub) › [Custom Systems](https://oxarus.com/en/hub/custom-systems)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [all on one screen.](#hero)
- [where do we start?](#audiences)
- [everyone sees their own work.](#roles)
- [one record from quote to invoice.](#approvals)
- [every job has an owner and a deadline.](#service)
- [rules take over repeated work.](#automation)
- [the numbers are ready each morning.](#reports)
- [a system that fits you.](#compare)
- [years of data, nothing lost.](#migration)
- [in use in four steps.](#process)
- [your questions.](#faq)
- [let's untangle the mess.](#cta)
## all on one screen.
_HUB · CUSTOM SYSTEMS_
No more orders stuck in Excel, requests buried in WhatsApp and notes on paper. We build a dashboard around the way you already work and automate the steps you repeat.
- [Get in touch](https://oxarus.com/en/hub/custom-systems#cta-heading) → `open_page(path="/hub/custom-systems", anchor="cta-heading")`
- [What we build](https://oxarus.com/en/hub/custom-systems#roles-heading) → `open_page(path="/hub/custom-systems", anchor="roles-heading")`
- No per-user fees
- Your Excel data comes with you
- Works on mobile too
1. Scattered
2. One dashboard
3. Automatic
_Representative interface data_ · Illustrative dashboard interface.
- **tabTitle:** Dashboard · Northfield Supply
- **excelName:** order\_tracking\_FINAL\_v3.xlsx
| | | |
| --- | --- | --- |
| Customer | Product | Status |
| Yıldız İnşaat | Plaster 40 bags | ?? |
| Ece Mimarlık | Tiles 60 m² | shipped?? |
| Demir Usta | Paint 12 buckets | CALL |
- **whatsappName:** Warehouse · Hakan
- Did Yıldız's plaster go out?
- Think we're down to 20
- Call Ece back!
- Invoice not sent yet?
- **mailSubject:** RE: RE: RE: stock status
- **mailFrom:** accounting@
- **company:** Northfield Supply
Dashboard · Orders · Inventory · Customers · Service · Reports
- **greeting:** Good morning, Murat
- **date:** Monday, September 14
- **Orders today**
- **value:** 24
- **delta:** +6
- **Awaiting approval**
- **value:** 3
- **Low stock**
- **value:** 5
- **Open service jobs**
- **value:** 7
- **delta:** -2
**Recent orders**
- 0
- **no:** #2041
- **customer:** Yıldız İnşaat
- **item:** Plaster · 40 bags
- **amount:** ₺18,400
- **status:** New
- 1
- **no:** #2040
- **customer:** Ece Mimarlık
- **item:** Tiles · 60 m²
- **amount:** ₺42,900
- **status:** In transit
- 2
- **no:** #2039
- **customer:** Demir Usta
- **item:** Paint · 12 buckets
- **amount:** ₺9,360
- **status:** Preparing
- 3
- **no:** #2038
- **customer:** Kaya Dekorasyon
- **item:** Parquet · 85 m²
- **amount:** ₺61,200
- **status:** Delivered
- **new:** New
- **transit:** In transit
- **preparing:** Preparing
- **delivered:** Delivered
**This week**
- Mo
- Tu
- We
- Th
- Fr
- Sa
62 · 78 · 54 · 88 · 96 · 40
**Automation · New order**
1. **Order received** · _Web form · Yıldız İnşaat_
2. **Stock reserved** · _Plaster · 40 bags, 180 left_
3. **Warehouse work order** · _Added to Hakan's list_
4. **Invoice draft** · _Sent to Logo_
5. **SMS to customer** · _“Your order is being prepared”_
- **toast:** Work order #2041 sent to the warehouse
- **auto:** Automatic
- **importing:** Importing
- 0
- **no:** #2037
- **customer:** Kaya Dekorasyon
- **item:** Skirting · 40 m
- **amount:** ₺6,800
- **status:** Delivered
- 1
- **no:** #2036
- **customer:** Yıldız İnşaat
- **item:** Plasterboard · 120 sheets
- **amount:** ₺27,600
- **status:** In transit
- **revenueLabel:** Revenue
## where do we start?
_WHAT'S SCATTERED_
In most companies, not everything is a mess at once; one process slows down the rest. We start where you lose the most time.
_Representative interface data_ · Representative
**From scattered notes to records**
> Representative
- **replay:** Play again
- **sourcesLabel:** Where it lives today
- **recordLabel:** In the dashboard
- **waiting:** Waiting
- **One flow from order to shipment** · _Orders and inventory_
“Orders go into Excel, stock lives in a separate file. The warehouse says it's there, the system says it isn't, and customers get the wrong promise.”
The moment an order is entered, stock is reserved, the warehouse gets the job and the shipment is tracked. Nobody types the same thing twice.
- Live stock with low-stock alerts
- Warehouse and shipping screen
- Bulk orders and price lists
- Automatic sync to accounting
- [See the order automation](https://oxarus.com/en/hub/custom-systems#automation-heading) → `open_page(path="/hub/custom-systems", anchor="automation-heading")`
- _Representative interface data_ · Representative
- **order\_tracking\_FINAL\_v3.xlsx**
| | | |
| --- | --- | --- |
| Customer | Product | Status |
| Yıldız İnşaat | Plaster 40 bags | ?? |
| Ece Mimarlık | Tiles 60 m² | shipped?? |
| Demir Usta | Paint 12 buckets | CALL |
- **Warehouse · Hakan**
- Did Yıldız's plaster go out?
- Think we're down to 20
- _Representative interface data_ · Representative
**Order #2041**
- **status:** Preparing
- **Customer:** Yıldız İnşaat
- **Product:** Plaster · 40 bags
- **Status:** Being prepared in the warehouse
- **Stock left:** 180 bags
- **Owner:** Hakan · Warehouse
- **Your field team, in the same dashboard** · _Service and field teams_
“Fault reports come in by phone, the team waits for jobs in a WhatsApp group, and nobody knows what got closed until evening.”
A ticket is opened, assigned to the right technician and closed from a phone with photos and a signature. The customer gets status updates by SMS.
- Work orders and assignment
- Mobile field screen
- Photos, signatures and parts log
- Service time reports
- [See the service board](https://oxarus.com/en/hub/custom-systems#service-heading) → `open_page(path="/hub/custom-systems", anchor="service-heading")`
- _Representative interface data_ · Representative
- **Phone note**
- Kaya Dekorasyon called
- Living room parquet has lifted
- Someone must go today!
- **Field team**
- Who's going to Kaya today?
- Emre: I'm free after 14:00
- Don't forget the photos
- _Representative interface data_ · Representative
**Service job #S-318**
- **status:** Assigned
- **Customer:** Kaya Dekorasyon
- **Fault:** Lifted parquet · living room
- **Due:** Today by 18:00
- **Technician:** Emre · 14:00
- **Closing:** With photos and a customer signature
- **Customer tracking built around you** · _Customer tracking_
“Quotes get lost in email, nobody knows who called whom, and when a salesperson leaves, the customer knowledge leaves with them.”
Every customer's quotes, calls, orders and balance on a single card. Reminders show up on their own.
- Quote and approval flow
- Call and reminder log
- Sales pipeline and targets
- No per-user fees
- [See the quote flow](https://oxarus.com/en/hub/custom-systems#approvals-heading) → `open_page(path="/hub/custom-systems", anchor="approvals-heading")`
- _Representative interface data_ · Representative
- **Ece Mimarlık**
- RE: RE: RE: tile quote
- Could you resend last week's price?
- We talked about 10% off.
- **Note**
- Call Ece back!
- Who had the quote?
- _Representative interface data_ · Representative
**Customer card · Ece Mimarlık**
- **status:** Open quote
- **Quote:** T-1182 · Tiles 60 m²
- **Discount:** 10% · with the manager for approval
- **Account owner:** Selin · Sales
- **Last contact:** Last week · asked for the price
- **Reminder:** Tomorrow 10:00 · call Ece
- **HR in one place** · _Staff and leave_
“Leave requests are on paper, overtime is calculated by hand, and advances and company equipment are tracked in separate spreadsheets.”
Leave is requested from a phone, a manager approves it and the balance updates automatically. Overtime, advances and assigned equipment live in the same record.
- Leave and approval flow
- Overtime and shift tracking
- Advances and equipment log
- Payroll export
- [See the role screens](https://oxarus.com/en/hub/custom-systems#roles-heading) → `open_page(path="/hub/custom-systems", anchor="roles-heading")`
- _Representative interface data_ · Representative
- **Leave form**
- Name: Hakan Y.
- September 22–24 · 3 days
- Approved by: \_\_\_\_\_\_\_\_
- **overtime\_sept\_FINAL.xlsx**
| | | |
| --- | --- | --- |
| Name | Overtime | Advance |
| Hakan | 6 hours | ₺2,000 |
| Emre | 4.5 hours | none |
- _Representative interface data_ · Representative
**Leave request · Hakan**
- **status:** Approved
- **Dates:** September 22–24 · 3 days
- **Approved by:** Murat · from his phone
- **Leave left:** Down from 11 days to 8
- **September overtime:** 6 hours · goes to payroll
- **Advance:** ₺2,000 · deducted from salary
_Interface labels:_ Today · What we build
## everyone sees their own work.
_WHO SEES WHAT_
The same order looks different to the manager, sales, the warehouse, the field team and accounting. We decide with you who can see and change what, and every change is logged.
- **Operations dashboard** · _DASHBOARD_
See orders, stock, service and team status on one screen. Every role sees its own work.
- Role-based home screen
- Live numbers and alerts
- Works on phone and tablet
- **Who sees what** · _ACCESS_
The warehouse doesn't see prices, sales doesn't see costs. Every user's permissions and every change they make are logged.
- Role and user permissions
- Change history
- Two-factor sign-in
_Representative interface data_ · Representative
**Role view**
> Representative
- **viewAs:** Whose screen
- **reset:** Reset
- **Murat**
- **role:** Manager
- **homeTitle:** Waiting for approval
- **Quote T-1182 · 10% off** · _Ece Mimarlık · sent by Selin_
- **action:** Approve
- **done:** Approved
- **Leave request · Hakan · 3 days** · _September 22–24_
- **action:** Approve
- **done:** Approved
- **Low stock · Paint** · _8 buckets left, minimum 10_
- **action:** Reorder
- **done:** Reordered
- **Selin**
- **role:** Sales
- **homeTitle:** Calls for today
- **Call Ece** · _Quote T-1182 · 10:00_
- **action:** Called
- **done:** Call logged
- **Demir Usta · paint order** · _Waiting for a price_
- **action:** Send quote
- **done:** Quote sent
- **Kaya Dekorasyon · new project** · _Parquet, about 200 m²_
- **action:** Open task
- **done:** Task opened
- **Hakan**
- **role:** Warehouse
- **homeTitle:** Orders to prepare
- **#2041 · Plaster · 40 bags** · _Shelf B-14 · Yıldız İnşaat_
- **action:** Ready
- **done:** Ready to ship
- **#2039 · Paint · 12 buckets** · _Shelf D-03 · Demir Usta_
- **action:** Ready
- **done:** Ready to ship
- **Stock count · Tiles** · _Aisle C · 14 items_
- **action:** Start
- **done:** Count started
- **Emre**
- **role:** Field
- **homeTitle:** Today's service jobs
- **S-318 · Kaya Dekorasyon** · _Lifted parquet · 14:00_
- **action:** On my way
- **done:** On the way
- **S-319 · Ece Mimarlık** · _Grout check · 16:30_
- **action:** On my way
- **done:** On the way
- **Part request · skirting** · _2 meters for S-318_
- **action:** Request
- **done:** Sent to warehouse
- **Aylin**
- **role:** Accounting
- **homeTitle:** Invoices to issue
- **#2040 · Ece Mimarlık** · _e-Invoice · ₺42,900_
- **action:** Issue invoice
- **done:** Sent to Logo
- **#2038 · Kaya Dekorasyon** · _3 days overdue_
- **action:** Remind
- **done:** SMS sent
- **Hakan · advance** · _₺2,000 · September payroll_
- **action:** Record
- **done:** Added to payroll
- **greeting:** Good morning, {name}
- **recordTitle:** Order #2041
- **Order #2041:** Record
- **permissions:** Permissions
- Customer
- Product and quantity
- Delivery
- Sale amount
- Cost and margin
- Shelf
- Account balance
- Proof of delivery
- **customer:** Yıldız İnşaat
- **product:** Plaster · 40 bags
- **delivery:** Building site · September 15
- **margin:** {cost} · {margin} margin
- **shelf:** B-14
- **balance:** {balance} · {limit} limit
- **proof:** Photos and signature pending
- **edit:** Can edit
- **view:** Can view
- **hidden:** Hidden
- **hiddenValue:** Hidden for this role
- **fieldColumn:** Field
**Change history**
- Selin created the order
- Hakan set the status to Preparing
- **entry:** {name} · {title}: {done}
## one record from quote to invoice.
_QUOTES AND APPROVALS_
Quotes are prepared on the customer card. A discount above what sales may give goes to a manager for approval; the approved quote becomes an order, and the order becomes an invoice. Who did what, and when, stays on record.
**Customer and quote tracking**
_CUSTOMERS_
Quotes, calls, orders and collections on the same customer card. The sales team may change; the knowledge stays with the company.
- Quote and approval flow
- Reminders and tasks
- Balance and collections
_Representative interface data_ · Representative
**Quote T-1182**
> Representative
- **restart:** Start over
**Ece Mimarlık**
- **type:** Architecture studio · customer for 2 years
- **Contact:** Ece
- **Account owner:** Selin · Sales
- **balanceLabel:** Open balance
**Recent activity**
- Yesterday · Selin called, they asked for the price again
- Last week · quote sent by email
- August · #1987 delivered
- **Reminder:** Tomorrow 10:00 · call Ece
1. Quote
2. Approval
3. Order
4. Invoice
- **waiting:** Waiting
- **current:** Now
- **done:** Done
- **skipped:** Not needed
- **product:** Tiles · 60 m²
- **unitPrice:** {price} per m²
> Selin can give up to {limit} off.
- **needsApproval:** {discount} off needs Murat's approval.
- **withinLimit:** Within sales authority, no approval needed.
- **subtotal:** Subtotal
- **Discount:** Discount
- **vat:** VAT {rate}
- **total:** Total
- **sendApproval:** Send for approval
- **sendCustomer:** Send to customer
- **approve:** Approve as Murat
- **reject:** Send back
- **order:** Convert to order
- **invoice:** Issue invoice
- **approval:** Waiting for Murat's approval
- **customer:** Waiting for Ece's reply
- **invoice:** Aylin will issue the invoice
- **done:** Invoice issued, e-invoice sent to Logo.
**Activity**
- **created:** Selin prepared the quote
- **sentApproval:** Selin sent it for approval at {discount} off
- **approved:** Murat approved
- **rejected:** Murat sent it back: {limit} at most
- **sentCustomer:** Quote emailed to Ece
- **ordered:** Ece accepted, #2040 opened and stock reserved
- **invoiced:** Aylin issued the invoice, sent to Logo
## every job has an owner and a deadline.
_SERVICE AND FIELD WORK_
A fault report becomes a job and goes to the right technician. The dashboard warns you as the promised time runs down; the job is closed from a phone with photos and a signature, and the customer is updated by SMS.
_Representative interface data_ · Representative
**Service board**
> Representative
- **now:** Time
- **speed:** 1 second = 5 minutes
- **reset:** Reset
- New
- Assigned
- On site
- Closed
- 0
- **no:** S-316
- **customer:** Yıldız İnşaat
- **issue:** Door frame fitting check
- **place:** Building site
- 1
- **no:** S-317
- **customer:** Yıldız İnşaat
- **issue:** Plasterboard arrived damaged
- **place:** Building site
- 2
- **no:** S-318
- **customer:** Kaya Dekorasyon
- **issue:** Lifted parquet in the living room
- **place:** Apartment
- 3
- **no:** S-319
- **customer:** Ece Mimarlık
- **issue:** Tile grout check
- **place:** Office
- 4
- **no:** S-320
- **customer:** Demir Usta
- **issue:** Paint mixer breakdown
- **place:** Shop
- 5
- **no:** S-321
- **customer:** Kaya Dekorasyon
- **issue:** Skirting fitting
- **place:** Apartment
- 6
- **no:** S-322
- **customer:** Ece Mimarlık
- **issue:** Bathroom tile survey
- **place:** Building site
- 7
- **no:** S-315
- **customer:** Demir Usta
- **issue:** Color chart and sample delivery
- **place:** Shop
- Emre
- Burak
- Deniz
- **left:** {time} left
- **late:** {time} late
- **onTime:** Closed on time
- **closedLate:** Closed late
- **hours:** {h} h {m} min
- **minutes:** {m} min
- **unassigned:** Unassigned
- **selectHint:** Pick a job to see its details.
- **assign:** Assign a technician
- **start:** Mark on site
- **proofLabel:** To close
- **photo:** Add photos
- **photoDone:** 2 photos added
- **signature:** Get signature
- **signatureDone:** Signed
- **close:** Close job
- **needProof:** A job can't close without photos and a signature.
> Job closed, report sent to the customer.
- **phoneTitle:** Field screen
**SMS to the customer**
- **assigned:** {tech} has been assigned to your service job {no}.
- **onsite:** Our technician {tech} has arrived.
- **closed:** {no} is closed. A report with photos was sent to your email.
- **escalation:** {time} left on {no}, Murat has been notified.
## rules take over repeated work.
_AUTOMATION AND INTEGRATIONS_
We turn the steps you repeat by hand every day into rules anyone can read. When a rule runs, the log shows what went to your accounting software, e-invoicing or WhatsApp.
- **Steps that run themselves** · _AUTOMATION_
We turn the manual work you do every day into rules: approvals, notifications, work orders, invoice drafts.
- SMS, email, WhatsApp notifications
- Approval and escalation rules
- Scheduled tasks
- **Accounting and ERP integration** · _INTEGRATIONS_
Talks to Logo, Mikro, Netsis or Paraşüt. You never enter the same data in two systems.
- Account and stock matching
- Invoice and delivery note sync
- Bank and email connections
_Representative interface data_ · Representative
**Rules**
> Representative
- **when:** Trigger
- **then:** Actions
- **on:** On
- **toggle:** Turn the rule on or off
- **run:** Run now
- **logTitle:** Run log
> Live
- **skipped:** Skipped: rule is off
- **seconds:** {value} s
- **accountingLabel:** Your accounting software
> Names show systems we can connect to; they do not imply a partnership.
- **#2042 approved · Kaya Dekorasyon**
- **trigger:** When an order is approved
- Reserve stock
- Open a warehouse work order
- Send the customer a WhatsApp message
- Send a draft invoice to accounting
- Parquet · 85 m² reserved
- WO-5521 · on Hakan's list
- Template: your order is being prepared
- {accounting} · draft invoice created
- **Paint · 8 buckets left, minimum 10**
- **trigger:** When stock drops below its minimum
- Open a purchasing task
- Email Murat
- Task: 40 buckets of paint
- Email sent
- **S-317 · Yıldız İnşaat**
- **trigger:** 30 minutes before a service job is due
- Notify the team lead
- Text the customer
- Murat notified
- SMS: technician on the way
- **#2040 · Ece Mimarlık**
- **trigger:** When an invoice is issued
- Create the e-invoice or e-archive invoice
- Email the PDF to the customer
- e-Invoice sent
- Email sent
- **₺42,900 · Ece Mimarlık**
- **trigger:** When a payment reaches the bank
- Match the payment to the account
- Post the collection to accounting
- #2040 paid
- {accounting} · collection posted
- **Weekly report time**
- **trigger:** Every Monday at 08:00
- Build the sales report as Excel
- Email it to management
- weekly\_sales.xlsx
- Sent to 3 people
**Connected systems**
- **Logo**
- **group:** Accounting
- **Mikro**
- **group:** Accounting
- **Netsis**
- **group:** Accounting
- **Paraşüt**
- **group:** Accounting
- **e-Invoice and e-Archive**
- **group:** Invoicing
- **WhatsApp Business**
- **group:** Messaging
- **SMS**
- **group:** Messaging
- **Email**
- **group:** Messaging
- **Bank transactions**
- **group:** Collections
- **Excel and CSV**
- **group:** Files
## the numbers are ready each morning.
_REPORTS_
Sales, stock turnover, service times and workload come from the same records. Filter a report and take it as Excel or PDF.
**Reports and exports**
_REPORTS_
Weekly sales, inventory turnover, service times, staff performance. Any report can go to Excel too.
- Ready-made management reports
- Filterable tables
- Excel and PDF export
_Representative interface data_ · Representative
**Reports**
> Representative
This week · This month · Last 3 months
- **week:** Week {week}
- **previous:** Vs previous period
- **highest:** Highest
- **breakdown:** Breakdown
- **share:** Share
- **exportLabel:** Export
- **preparing:** Preparing
- **ready:** {file} is ready
- **days:** {value} days
- **hours:** {value} h
- **jobs:** {value} jobs
- **thousands:** ₺{value}k
- _Sales_
- **total:** Total sales
- **by:** By customer
- **file:** sales\_report
- Yıldız İnşaat
- Ece Mimarlık
- Kaya Dekorasyon
- Demir Usta
- _Stock turnover_
- **total:** Average days to turn over
- **by:** By product
- **file:** stock\_turnover\_report
- Plaster
- Tiles
- Paint
- Parquet
- _Service time_
- **total:** Average time to close
- **by:** By job type
- **file:** service\_time\_report
- Fitting
- Breakdown
- Inspection
- Delivery damage
- _Workload_
- **total:** Jobs closed
- **by:** By person
- **file:** workload\_report
- Hakan
- Emre
- Selin
- Aylin
## a system that fits you.
_EXCEL, OFF-THE-SHELF, CUSTOM_
Excel is cheap to start with but breeds errors as you grow. Off-the-shelf software is orderly, but it runs on its own templates, not on how your business works.
| | EXCEL AND OFF-THE-SHELF | A SYSTEM BUILT FOR YOU |
| --- | --- | --- |
| A fee for every user? | Monthly per-user licenses: The bill grows with the team; even giving warehouse staff an account costs money. | No user limit: Built once. Use it with 5 people or 500. |
| Does it fit your workflow? | You adapt to the software: The team is forced to work around the software's fields and steps, and whatever doesn't fit ends up back in Excel. | The software adapts to you: Forms, approval steps and reports are designed around the way you work today. |
| Who holds the data? | In files or with the vendor: Excel files sit on personal computers; with off-the-shelf software, your data lives on the vendor's servers. | Your company: The database and source code are yours. Backups and access are under your control. |
| Errors and rework? | Same data, typed in several places: When orders, stock and invoices live in different places, the numbers never match and every month ends with a reconciliation. | Data is entered once: The moment an order is entered, inventory, warehouse and accounting all see the same data. |
_Representative interface data_ · Representative
> Representative
**As users are added**
- **pick:** Users
- **users:** {count} users
- **EXCEL AND OFF-THE-SHELF:** {count} user licenses
- **A SYSTEM BUILT FOR YOU:** No user licenses
**Order form**
**EXCEL AND OFF-THE-SHELF**
- Customer
- Product
- Quantity
- Notes
**EXCEL AND OFF-THE-SHELF**
- Yıldız İnşaat
- Plaster
- 40
> site in Çekmeköy, deliver Friday, Ali's truck
- **missing:** No field on the form
**A SYSTEM BUILT FOR YOU**
- Customer
- Product and unit
- Site address
- Delivery day
- Truck and driver
**A SYSTEM BUILT FOR YOU**
- Yıldız İnşaat
- Plaster · 40 bags
- Çekmeköy site
- Friday
- 34 ABC 12 · Ali
**Where the data lives**
**EXCEL AND OFF-THE-SHELF**
- The accounting PC
- A salesperson's laptop
- The vendor's server
**A SYSTEM BUILT FOR YOU**
- Database
- Source code
- Backups
- Access rights
- **yours:** Yours
**How many places one order is typed**
- Excel
- Accounting software
- WhatsApp
- 40 bags
- 45 bags
- 4 bags
- **mismatch:** The numbers don't match
- **once:** Entered once
- Stock
- Warehouse
- Accounting
- **value:** 40 bags
## years of data, nothing lost.
_DATA MIGRATION_
We clean up your Excel files, records from old software and customer lists, then move them into the new system. You don't start day one with an empty screen.
**From**
- Excel files
- Google Sheets
- Legacy software
- Logo / Mikro
- Email archive
- Paper forms
- **To:** A dashboard built for your company
> The database and code are yours; no user limit.
_Representative interface data_ · Illustrative figures.
- **Customer records:** 3,840
- **Stock items:** 1,260
- **Past orders:** 27,450
- **Service records:** 8,920
- Duplicate records removed
- Wrong and missing fields fixed
- Old and new systems run side by side briefly
- Post-migration verification report
- **queued:** Queued
- **running:** Moving
- **verified:** Checked
**Clean-up**
- 0
- **before:** YILDIZ INŞ. / Yıldız İnşaat
- **rule:** Same customer merged
> Yıldız İnşaat
- 1
- **rule:** Status picked from a list
shipped??
> In transit
- 2
- **before:** Paint 12 buckets
- **rule:** Product, quantity and unit split
> Paint · 12 · buckets
- 3
- **before:** Phone: empty
- **rule:** Flagged to be filled in
> Missing field
#### Switchover
- **open old:** Old files still in use
- **open new:** The dashboard is the only source
_Interface labels:_ Play migration · Play again
## in use in four steps.
_HOW WE WORK_
First we learn your business, then we sketch the screens with you.
1. **Discovery** · _WEEKS 1–2_
We sit down with your team and watch how work actually gets done today: which files, which messages, which approvals.
**What you get**
- Workflow map
- Priority order
- Clear price and timeline
2. **Design** · _WEEKS 3–4_
We sketch the screens for every role, then refine them as your team tries out a clickable prototype.
**What you get**
- Role-based screen designs
- Clickable prototype
- Team feedback round
3. **Build** · _WEEKS 5–10_
We build the system, connect it to accounting and your other software, and migrate your data. You see a working version every two weeks.
**What you get**
- A build every two weeks
- Integrations and automations
- Data migration report
4. **Rollout** · _WEEK 10+_
We train your team and stay close through the first weeks. As new needs come up, we keep growing the system.
**What you get**
- User training
- Live support
- Development and maintenance options
_Representative interface data_ · Representative
> Representative
- **map:** Workflow map
- Order
- Stock
- Warehouse
- Shipping
- Invoice
- Excel
- WhatsApp
- Paper
- Phone
- Email
- **screens:** Role screens
- Manager
- Sales
- Warehouse
- Field
- Accounting
- **builds:** A build every two weeks
- Orders and stock
- Warehouse and service
- Accounting link
- **buildWeek:** Week {week}
- **rollout:** Teams on the dashboard
- Management
- Sales
- Warehouse
- Field
- Accounting
_Interface labels:_ STEP
## your questions.
_FAQ_
Don't see your question here? Write to us.
**Question:** Why a custom system when off-the-shelf software exists?
**Answer:** If your business fits an off-the-shelf product, we'll recommend it and say so plainly. If per-user fees keep growing, half the work still runs in Excel, or you have a workflow unique to you, a custom system is cheaper and more efficient in the long run.
**Question:** My team isn't very tech-savvy. Can they use it?
**Answer:** We design the screens around the language and routines your team already uses, and each role sees only its own work. We train everyone before launch and stay close through the first weeks.
**Question:** What happens to our Excel data?
**Answer:** We review your files, weed out duplicate and faulty records, and migrate the rest into the new system. Old and new run side by side for a short while, and once the numbers match, the switch is complete.
**Question:** Will it work with our accounting software?
**Answer:** We often work with Logo, Mikro, Netsis and Paraşüt. Account, stock, invoice and delivery note data moves between both sides.
**Question:** Can it be used on phones and in the field?
**Answer:** Yes. The dashboard works on phones and tablets too. For field teams, we can add features like photos, location and signatures.
**Question:** How long does it take, and how is the cost set?
**Answer:** Most projects reach a first usable version in 8–10 weeks. Cost depends on the number of screens and integrations; at the end of discovery, we give you a fixed price and timeline.
**Question:** Can we add features later?
**Answer:** Yes. The system is yours, so it grows as your needs do. We can continue with monthly development support or on a per-project basis, whichever you prefer.
> **Let's go over your work**
>
> No commitment, just a short call
>
> Tell us which work runs on Excel, WhatsApp or paper today. We'll figure out together where it makes sense to start.
> - [Request a call](mailto:info@oxarus.com) → `contact()`
## let's untangle the mess.
_LET'S START_
Just tell us which task takes up most of your time.
- [Get in touch](mailto:info@oxarus.com) → `contact()`
_Interface labels:_ Copied
## Actions
- [Get in touch](https://oxarus.com/en/hub/custom-systems#cta-heading) → `open_page(path="/hub/custom-systems", anchor="cta-heading")`
- [What we build](https://oxarus.com/en/hub/custom-systems#roles-heading) → `open_page(path="/hub/custom-systems", anchor="roles-heading")`
- [See the order automation](https://oxarus.com/en/hub/custom-systems#automation-heading) → `open_page(path="/hub/custom-systems", anchor="automation-heading")`
- [See the service board](https://oxarus.com/en/hub/custom-systems#service-heading) → `open_page(path="/hub/custom-systems", anchor="service-heading")`
- [See the quote flow](https://oxarus.com/en/hub/custom-systems#approvals-heading) → `open_page(path="/hub/custom-systems", anchor="approvals-heading")`
- [Request a call](mailto:info@oxarus.com) → `contact()`
- [Türkçe](https://oxarus.com/tr/hub/custom-systems) → `switch_locale(locale="tr", path="/hub/custom-systems")`
## Related pages
- [Oxarus Hub](https://oxarus.com/en/hub)
---
title: "Product, design and mobile app development · Oxarus Studio"
description: "Oxarus Studio runs its own education product, Pals, and builds web platforms, code-first interfaces and iOS/Android apps for clients."
url: https://oxarus.com/en/studio
key: studio
route: /studio
unit: studio
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/studio
en: https://oxarus.com/en/studio
documents:
json: https://oxarus.com/machine/en/studio.json
jsonld: https://oxarus.com/machine/en/studio.jsonld
txt: https://oxarus.com/machine/en/studio.txt
schema: oxarus.machine/2.0
---
# Product, design and mobile app development · Oxarus Studio
> Oxarus Studio runs its own education product, Pals, and builds web platforms, code-first interfaces and iOS/Android apps for clients.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Studio](https://oxarus.com/en/studio)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [product, end to end.](#hero)
- [four areas, one discipline.](#areas)
- [every discipline, one product.](#team)
- [built for ourselves first.](#proof)
- [tell us what you want to build.](#cta)
## product, end to end.
_OXARUS STUDIO_
We run our own product, Pals, every day. With the same discipline, we build web platforms, interface design and iOS/Android apps for clients.
- [Tell us about your project](https://oxarus.com/en/studio#cta-heading) → `open_page(path="/studio", anchor="cta-heading")`
- [See the areas](https://oxarus.com/en/studio#areas) → `open_page(path="/studio", anchor="areas")`
- Strategy, design and code in one process
- Web, iOS and Android together
- Still accountable after launch
1. Pals
2. Product development
3. Design
4. Mobile
_Representative interface data_ · Illustrative product screens.
- **workspace:** studio / active work
- **open:** View
> Representative
- **Pals** · _Our own product_
- [Pals](https://oxarus.com/en/studio/pals)
- **Product development** · _Routely_
- [Product development](https://oxarus.com/en/studio/services)
- **Design** · _Component system_
- [Design](https://oxarus.com/en/studio/design)
- **Mobile** · _Brewline_
- [Mobile](https://oxarus.com/en/studio/mobile)
- **teacher:** Selin Aydın
- **role:** Math · 11-B
- **task:** Derivative exercises
- **due:** Friday 17:00
- **submitted:** submitted
- Ela Demir
- Kerem Yıldız
- Deniz Kaya
- **done:** Submitted
- **pending:** Pending
- **attendance:** Attendance · 27/28
- **notified:** Parents notified
**Today's deliveries**
> Live
- **In transit**
- **Delivered**
- **Avg. time** · _min_
- 0
- **no:** #8841
- **customer:** Bluebell Pharmacy
- **status:** In transit
- 1
- **no:** #8840
- **customer:** Northside Market
- **status:** Delivered
- 2
- **no:** #8836
- **customer:** Parkview Optics
- **status:** Delay risk
- **rerouted:** Rerouted
- **component:** Button / primary
**states**
- Default
- Hover
- Pressed
- Loading
- Disabled
- **action:** Confirm order
- **tokens:** Color tokens
- **motion:** Motion curve
- **greeting:** Good morning, Sophia
- **order:** Oat flat white
- **ready:** Ready in 3 min
1. Received
2. Preparing
3. Ready
- **offline:** Offline · 2 actions queued
- **synced:** Back online · synced
- **push:** Ready notification sent
- **release:** New release in both stores
## four areas, one discipline.
_AREAS_
Each area has working examples on its own page. Open a column and try the small demo.
- **Pals** · _Our own product_
A portal for educational institutions. Timetables, homework, attendance and payments in one place; live at EduNeta.
- Roles and permissions your institution defines
- Modules switched on per institution
- Web, iOS and Android
- [Pals](https://oxarus.com/en/studio/pals)
- **Product development** · _Client work_
SaaS, marketplace, booking and field apps. From prototype to launch, with the code in your name.
- Clickable prototype by week 3
- Web dashboard and mobile app together
- You keep the source code and accounts
- [Product development](https://oxarus.com/en/studio/services)
- **Interface design** · _Designed in code_
We deliver interfaces as working components, not pictures. Loading, error and success states included.
- Every state of every component
- Color and spacing tokens
- Restrained motion and transitions
- [Interface design](https://oxarus.com/en/studio/design)
- **Mobile systems** · _iOS · Android_
Apps that keep working when the connection drops and notify at the right moment. Store launch and everything after is on us.
- Offline mode and sync
- Camera, location, notifications
- Post-launch crash and version tracking
- [Mobile systems](https://oxarus.com/en/studio/mobile)
_Representative interface data_
> Demos are representative
**Roles**
- Teacher
- Parent
- Accounting
- **addRole:** Add role
- **customRole:** Guidance counselor
- Assigns homework
- Enters grades
- Sees payments
- Pulls reports
- **Roles:** {grants} permissions on
1. Prototype
2. Design
3. Live
- In transit
- Delivered
- Avg. min
- **liveBadge:** Live
- Default
- Hover
- Pressed
- Loading
- Done
- **button:** Save
- App Store
- Google Play
- Preparing
- In review
- Live
- **rolloutLabel:** Staged rollout share
- Submit for review
- Release
- Roll out to everyone
- Start over
- Homework
- Grades
- Payments
- Reports
- **menuLabel:** Shows in the menu
_Interface labels:_ Open page
## every discipline, one product.
_TEAM_
Strategy, design, web, mobile and infrastructure aren't scattered across separate vendors. Pick an area or a discipline to see who leads the work and who carries each step.
- **count suffix:** disciplines involved
#### How the work flows
- **Strategy**
- **short:** Strategy
> Sets the scope, the priorities and what stays out of the first release.
- **User experience**
- **short:** UX
> Shapes flows and screen order around real user scenarios.
- **Interface**
- **short:** UI
> Ties color, typography and component states into the design system.
- **Web**
- **short:** Web
> Builds dashboards and web apps that are fast and accessible.
- **iOS**
- **short:** iOS
> Builds the iPhone app around device capabilities and App Store rules.
- **Android**
- **short:** Android
> Builds the Android app, testing it across screen sizes and OS versions.
- **Backend**
- **short:** Backend
> Sets up the data model, permissions and third-party service integrations.
- **DevOps**
- **short:** DevOps
> Runs the release pipeline, monitoring, backups and store distribution.
- **Pals**
It's our own product, so every discipline owns the work. A new module moves from strategy to launch under the same ownership.
**How the work flows**
- Needs from the institution are prioritized
- Impact on roles and permissions is mapped
- Web and both mobile apps ship together
- **Product development**
Strategy and backend build the skeleton; web and DevOps bring the product to life. Mobile joins the project when needed.
**How the work flows**
- Scope and first-release boundaries are written down
- The clickable prototype is tested with the client
- Code, accounts and docs are handed over
- **Interface design**
Design and web work in the same file. Every state that's drawn has its counterpart as a component in code.
**How the work flows**
- Flow and screen order are settled
- Tokens and component states are set up
- Components are wired into the product code
- **Mobile systems**
iOS and Android move forward side by side. DevOps manages store releases and health monitoring after launch.
**How the work flows**
- Offline and notification scenarios are mapped
- Both platforms are built in the same sprint
- Store review and version tracking are handled
_Interface labels:_ Discipline and area matrix · Supports · Not involved
## built for ourselves first.
_OUR OWN PRODUCT_
Pals is the portal we build and run for educational institutions. It's used every day at EduNeta on web, iOS and Android. Every method we recommend in client projects, we tried there first.
- Web, iOS and Android
- Flexible roles and permissions
- Active daily use
- [Explore Pals](https://oxarus.com/en/studio/pals) → `open_page(path="/studio/pals")`
> Live at EduNeta
_Representative interface data_
**Today's classes**
- **date:** Wed, Sep 16
- **Math · 9-A** · _09:00_
- **room:** B204
- **Physics · 10-C** · _10:30_
- **room:** Lab 2
- **Literature · 11-B** · _13:15_
- **room:** A108
- **attendance:** Attendance taken
- **address:** pals.eduneta.com.tr
- **now:** Now
- 9-A attendance saved: 27/28.
- 10-C attendance saved: 26/28.
- 11-B attendance saved, nobody absent.
## tell us what you want to build.
_STUDIO_
A platform, a mobile app or a new interface for your existing product. A few sentences is enough; we'll come back with a clear first take on scope, timeline and team.
- [Get in touch](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
> Pals, live at EduNeta
## Actions
- [Tell us about your project](https://oxarus.com/en/studio#cta-heading) → `open_page(path="/studio", anchor="cta-heading")`
- [See the areas](https://oxarus.com/en/studio#areas) → `open_page(path="/studio", anchor="areas")`
- [Explore Pals](https://oxarus.com/en/studio/pals) → `open_page(path="/studio/pals")`
- [Get in touch](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [Türkçe](https://oxarus.com/tr/studio) → `switch_locale(locale="tr", path="/studio")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
- [Pals](https://oxarus.com/en/studio/pals)
- [App Development](https://oxarus.com/en/studio/services)
- [Interactive Design](https://oxarus.com/en/studio/design)
- [Mobile](https://oxarus.com/en/studio/mobile)
---
title: "Pals: a portal for educational institutions"
description: "Timetables, homework, exams, attendance and payments in one app, with a screen each for students, parents, teachers and administrators."
url: https://oxarus.com/en/studio/pals
key: studio-pals
route: /studio/pals
unit: studio
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/studio/pals
en: https://oxarus.com/en/studio/pals
documents:
json: https://oxarus.com/machine/en/studio/pals.json
jsonld: https://oxarus.com/machine/en/studio/pals.jsonld
txt: https://oxarus.com/machine/en/studio/pals.txt
schema: oxarus.machine/2.0
---
# Pals: a portal for educational institutions
> Timetables, homework, exams, attendance and payments in one app, with a screen each for students, parents, teachers and administrators.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Studio](https://oxarus.com/en/studio) › [Pals](https://oxarus.com/en/studio/pals)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [school, in one app.](#hero)
- [a screen for every role.](#roles)
- [a school day.](#day)
- [school, end to end.](#modules)
- [under your name.](#brand)
- [see how it looks at your school.](#cta)
## school, in one app.
_STUDIO · PALS_
Timetables, homework, exams, attendance and payments in one place. What a teacher enters reaches students and parents at the same moment, so nobody has to call to ask.
- [Request a demo](https://oxarus.com/en/studio/pals#cta-heading) → `open_page(path="/studio/pals", anchor="cta-heading")`
- [Who sees what](https://oxarus.com/en/studio/pals#roles-heading) → `open_page(path="/studio/pals", anchor="roles-heading")`
- Web, iOS and Android
- In your institution's name and colors
- Everyone sees only their own screen
1. Teacher assigns
2. Student completes
3. Parent sees
_Representative interface data_ · Illustrative screens.
- **domain:** pals.eduneta.com.tr
- **tabTitle:** Homework · EduNeta
- **school:** EduNeta
- **formTitle:** New assignment
- **subject:** Derivative exercises
- **detail:** Textbook pages 42–45, even-numbered questions. Photograph and upload your solutions, and add a note on any question you got stuck on.
- **Due:** Friday, 17:00
- **send:** Send to class
- **sent:** Sent
**Submission status**
**Derivative exercises**
- **time:** 16:42
- **hello:** Hi Ela
- **Today's classes:** 6 classes today · 1 new assignment
- **newTag:** New
- **course:** Math
- **Due:** Due Friday 17:00
- **upload:** Solution photo attached
- **submit:** Submit
- **submitted:** Submitted
- **Next class:** Physics · 14:10 · Lab 2
Today · Homework · Exams · Profile
**Submitted this week**
- **done:** 7 assignments
- **uploadHint:** Add a solution photo
- **time:** 16:43
- **child:** Ela Demir · 11-A
- **hello:** Ela's day
- **Math homework submitted** · _Just now_
- **Attended all 6 classes today** · _15:20_
- **Physics exam grade posted: 88** · _12:05_
- **October installment paid** · _Yesterday_
- **meeting:** Parent meeting · Thursday 18:30
Summary · Grades · Payments · Messages
- **search:** Search…
- Classes
- Tracking
- Communication
- Institution
- **Today**
- **group:** 0
- **Timetable**
- **group:** 0
- **Homework**
- **group:** 0
- **count:** 3
- **Exams**
- **group:** 0
- **Mock exams**
- **group:** 0
- **count:** 2
- **Answer keys**
- **group:** 0
- **Study sessions**
- **group:** 0
- **Library**
- **group:** 0
- **Attendance**
- **group:** 1
- **Learning outcomes**
- **group:** 1
- **Guidance**
- **group:** 1
- **Reports**
- **group:** 1
- **Messages**
- **group:** 2
- **count:** 12
- **Parent meetings**
- **group:** 2
- **Announcements**
- **group:** 2
- **Leave requests**
- **group:** 3
- **Documents**
- **group:** 3
- Homework
- New assignment
- **11-A · Math** · _08:30_
- **state:** done
- **12-C · Math** · _10:10_
- **state:** done
- **11-A · Study session** · _13:20_
- **state:** now
- **Department meeting** · _15:00_
- **state:** next
- 11-A
- 11-B
- 12-C
- **attachment:** derivative-exercises.pdf
- **attachmentSize:** 1.2 MB
- **notifyParents:** Notify parents too
- **reminder:** Remind 1 day before it's due
- **audience:** 28 students · 26 parents
- **toast:** Reached 28 students and 26 parents
- **ringLabel:** submitted
**Recent activity**
- Ela Demir submitted
- Kerem Aslan submitted
- Zeynep Tunç uploaded a file
- Mert Kaya submitted
- Defne Yıldız submitted
- **now:** now
**Class homework completion this week**
- Mo
- Tu
- We
- Th
- Fr
> live
- **minutes:** min
**Learning outcomes**
- Definition of the derivative
- Product rule
- Chain rule
- Tangent line equation
**This month's assignments**
- **Limits and continuity**
- **rate:** 96
- **Graphs of functions**
- **rate:** 89
- **Logarithms review**
- **rate:** 92
- **previousTitle:** Limits and continuity
- _10:40_
- **line:** 12-C exam grades entered
- _09:00_
- **line:** Limits assignment closed
- _Yesterday_
- **line:** Department meeting notes shared
## a screen for every role.
_ROLES_
You start with student, parent, teacher, staff and management roles, and none of them are fixed. Your institution adds roles and decides, module by module, what each one can see and change.
_Representative interface data_ · Representative screen
- **screenTitle:** Home screen
**Permissions**
- View
- Edit
- Approve
- Homework
- Exams
- Payments
- Reports
> Roles aren't fixed: add your own, like guidance counselor, accounting or campus director.
_Representative interface data_ · Representative screen
- **appName:** EduNeta
_Representative interface data_ · Representative screen
- **scopeTitle:** Permission scope
**Custom roles**
- **Guidance counselor**
Which students should I meet this week?
- _Representative interface data_ · Representative screen
- 3 meetings this week
- 5 classes today
- Mock exam results in
- Thursday 16:00 · parent
- Attendance by class
- 1 new message
- _Representative interface data_ · Representative screen
> Mock exam results are in: 4 students dropped.
- _Representative interface data_ · Representative screen
- **noticeTime:** 10:50
- **Accounting**
Who paid this month, and who is late?
- _Representative interface data_ · Representative screen
- 7 payments today
- Collections report ready
- 2 contracts up for renewal
- Monthly summary
- 1 refund request
- No new messages
- _Representative interface data_ · Representative screen
> 7 of the November installments were paid today.
- _Representative interface data_ · Representative screen
- **noticeTime:** 17:40
- **Campus director**
How is my campus doing this week?
- _Representative interface data_ · Representative screen
- Weekly summary ready
- 9 absent today
- Collections tracking
- 1 announcement draft
- 2 open requests
- 4 unread messages
- _Representative interface data_ · Representative screen
> The weekly campus report is ready.
- _Representative interface data_ · Representative screen
- **noticeTime:** 08:30
- **Shuttle coordinator**
Which students won't ride the shuttle today?
- _Representative interface data_ · Representative screen
- 2 open requests
- Route notice draft
- 3 students absent today
- Parent meeting 18:00
- 1 leave request
- No new messages
- _Representative interface data_ · Representative screen
> 2 students won't use the shuttle today.
- _Representative interface data_ · Representative screen
- **noticeTime:** 07:15
_Representative interface data_ · Representative screen
- **grantedMeta:** Added with the new permission
_Representative interface data_ · Representative screen
- **program:** Timetable
- **homework:** Homework
- **exams:** Exams
- **study:** Study
- **library:** Library
- **messages:** Messages
- **summary:** Summary
- **absence:** Absences
- **payments:** Payments
- **meeting:** Meetings
- **attendance:** Attendance
- **guidance:** Guidance
- **requests:** Requests
- **leave:** Leave
- **meetings:** Meetings
- **notices:** Notices
- **reports:** Reports
- **finance:** Finance
- **contracts:** Contracts
- **announcements:** Announcements
- **Student**
What's on today, and what do I need to hand in?
- Daily timetable and study sessions
- Submit homework from a phone
- Exam results and topic gaps
- _Representative interface data_ · Representative screen
- 6 classes · first at 08:30
- 1 new, 2 pending
- Physics grade in
- 13:20 · Math
- 2 books due
- 12 unread messages
- _Representative interface data_ · Representative screen
> Math homework assigned, due Friday 17:00.
- _Representative interface data_ · Representative screen
- **noticeTime:** now
- **Parent**
Was my child in class? Did they do their homework?
- Absences reported instantly
- Grades and teacher comments
- Installments and payment history
- _Representative interface data_ · Representative screen
- Ela in 6/6 classes today
- 1 day this term
- Physics: 88
- October installment paid
- Thursday 18:30
- 2 messages from teachers
- _Representative interface data_ · Representative screen
> Ela submitted her math homework.
- _Representative interface data_ · Representative screen
- **noticeTime:** 2 min
- **Teacher**
Take attendance, assign homework, start class.
- One-tap attendance
- Assign homework and see submissions
- Answer keys and exam entry
- _Representative interface data_ · Representative screen
- 4 classes · next at 13:20
- 11-A · 2 absent
- 10/28 submitted
- 12-C grades pending
- 3 meeting notes
- 12 unread messages
- _Representative interface data_ · Representative screen
> 11-A attendance saved, 2 students absent.
- _Representative interface data_ · Representative screen
- **noticeTime:** 08:12
- **Staff**
A request came in. Who handles it?
- Handling support requests
- Resource and library tracking
- Leave and shift planning
- _Representative interface data_ · Representative screen
- 4 open · 1 urgent
- 12 books on loan
- 1 awaiting approval
- Department 15:00
- Shuttle notice draft
- 3 unread messages
- _Representative interface data_ · Representative screen
> New support request: shuttle times.
- _Representative interface data_ · Representative screen
- **noticeTime:** 15:30
- **Management**
How is the institution doing overall?
- Reports by grade and section
- Collections and contract tracking
- School-wide announcements
- _Representative interface data_ · Representative screen
- Weekly attendance 96%
- Collections 92%
- 2 contracts up for renewal
- 14 absent today
- Parent meeting draft
- 6 open requests
- _Representative interface data_ · Representative screen
> October collections report is ready.
- _Representative interface data_ · Representative screen
- **noticeTime:** 09:00
_Interface labels:_ Click the boxes: when a permission changes, the screen on the phone changes too. · Default
## a school day.
_ONE DAY_
The small things that happen throughout the day. Someone enters each one, and it reaches the right person automatically. Play the day or pick a time.
- **Attendance taken** · _08:10_
The teacher marks who's missing on the class list. Within minutes, a notification lands on the parent's phone.
- **from:** Teacher
- **to:** Parent
- _Representative interface data_ · Representative notifications
- **push:** Ela missed 1st period today.
- _Representative interface data_ · Representative notifications
- **pushWhen:** 08:12
- **Exam results entered** · _10:45_
Once grades are in, students see which topics they're behind on, and parents find out without waiting for the report card.
- **from:** Teacher
- **to:** Student, parent
- _Representative interface data_ · Representative notifications
- **push:** Your physics exam grade is out: 88.
- _Representative interface data_ · Representative notifications
- **pushWhen:** 10:46
- **Study session scheduled** · _13:20_
Free periods and teacher availability show up side by side. Once a session is added, it goes straight into the student's timetable.
- **from:** Guidance
- **to:** Student
- _Representative interface data_ · Representative notifications
- **push:** Study session added to your timetable: Math, 13:20.
- _Representative interface data_ · Representative notifications
- **pushWhen:** 13:21
- **Support request opened** · _15:30_
A parent asks about shuttle times. The request goes to the right staff member and closes once answered, so no message gets lost.
- **from:** Parent
- **to:** Staff
- _Representative interface data_ · Representative notifications
- **push:** Your request has been sent to the shuttle team.
- _Representative interface data_ · Representative notifications
- **pushWhen:** 15:31
- **Installment reminder sent** · _18:00_
Parents get a gentle reminder when a payment is coming due. Once it's paid, the accounting screen updates.
- **from:** System
- **to:** Parent, accounting
- _Representative interface data_ · Representative notifications
- **push:** Your November installment is due in 3 days.
- _Representative interface data_ · Representative notifications
- **pushWhen:** 18:00
- **Homework submitted** · _21:15_
The student photographs and uploads their solution. In the morning, the teacher sees who submitted on a single list.
- **from:** Student
- **to:** Teacher
- _Representative interface data_ · Representative notifications
- **push:** Kerem Aslan submitted his homework.
- _Representative interface data_ · Representative notifications
- **pushWhen:** 21:15
_Representative interface data_ · Representative notifications
- **appName:** EduNeta
_Representative interface data_ · Representative notifications
- **more:** {n} more notifications
_Interface labels:_ Play the day · Pause
## school, end to end.
_MODULES_
One portal instead of a stack of separate apps. Your institution chooses which modules to use.
- Classes
- Tracking
- Communication
- Administration
- **Timetable**
By section and room
- **sym:** Tt
- **Study sessions**
Set by free periods
- **sym:** St
- **Homework**
Submitted with files
- **sym:** Hw
- **Exams**
Grades and topics
- **sym:** Ex
- **Answer keys**
Bubble-sheet exams
- **sym:** Ak
- **Library**
Loans and returns
- **sym:** Lb
- **Attendance**
One tap per class
- **sym:** At
- **Guidance**
Counseling notes
- **sym:** Gd
- **Reports**
By grade and class
- **sym:** Rp
- **Leave**
Approval flow
- **sym:** Lv
- **Notifications**
Push, SMS, email
- **sym:** Nt
- **Messages**
Teachers, parents
- **sym:** Ms
- **Meetings**
Calendar and invites
- **sym:** Mt
- **Support requests**
Routed to staff
- **sym:** Sr
- **Payments**
Plans and receipts
- **sym:** Pm
- **Finance**
Collection reports
- **sym:** Fn
- **Contracts**
Enroll and renew
- **sym:** Ct
- **Permissions**
Role-based access
- **sym:** Pr
{on} / {total} modules on
**Menu preview**
> Representative
_Representative interface data_ · Representative
- **allOn:** Every module is on; the menu and permission tables are complete.
_Representative interface data_ · Representative
- **removed:** {modules} modules removed from the menu and from the permission table of the affected roles.
_Interface labels:_ Click a module you won't use to turn it off; it leaves the menu next to it and the permission table of every role too. · Turn all on · on · off
## under your name.
_MADE FOR YOUR SCHOOL_
The app sits in the store under your institution's name. The logo, colors and address are yours; students never run into another brand. Pick an institution, a color and a platform to try it.
- **EduNeta** · _live_ · _pals.eduneta.com.tr_
- **short:** EN
- **Brand color:** #6165ed
- **Harbor Academy** · _representative_
- **short:** HA
- **Brand color:** #08828e
- **Redline Tutoring** · _representative_
- **short:** RT
- **Brand color:** #d34236
_Representative interface data_
- **login:** Sign in
_Representative interface data_
- **userLabel:** Student number
_Representative interface data_
- **passLabel:** Password
**One account, three platforms**
Browser · iOS · Android
- Your school's address
- App Store
- Google Play
_Representative interface data_
- **Student number:** 2024-1187
_Representative interface data_
- **forgot:** Forgot password
_Representative interface data_
- **parentLogin:** Sign in as a parent
_Representative interface data_
- **welcome:** Welcome to the student and parent portal
_Interface labels:_ Pick an institution
## see how it looks at your school.
_DEMO_
Tell us how your institution is structured; we'll set up roles and modules to match and prepare a short demo.
- [Request a demo](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
> Pals is in daily use at an educational institution today.
## Actions
- [Request a demo](https://oxarus.com/en/studio/pals#cta-heading) → `open_page(path="/studio/pals", anchor="cta-heading")`
- [Who sees what](https://oxarus.com/en/studio/pals#roles-heading) → `open_page(path="/studio/pals", anchor="roles-heading")`
- [Request a demo](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [Türkçe](https://oxarus.com/tr/studio/pals) → `switch_locale(locale="tr", path="/studio/pals")`
## Related pages
- [Oxarus Studio](https://oxarus.com/en/studio)
---
title: "Custom application engineering · Oxarus Studio"
description: "We build the web platform and mobile app you'll offer your customers, from idea to launch, then keep growing it with you."
url: https://oxarus.com/en/studio/services
key: studio-services
route: /studio/services
unit: studio
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/studio/services
en: https://oxarus.com/en/studio/services
documents:
json: https://oxarus.com/machine/en/studio/services.json
jsonld: https://oxarus.com/machine/en/studio/services.jsonld
txt: https://oxarus.com/machine/en/studio/services.txt
schema: oxarus.machine/2.0
---
# Custom application engineering · Oxarus Studio
> We build the web platform and mobile app you'll offer your customers, from idea to launch, then keep growing it with you.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Studio](https://oxarus.com/en/studio) › [App Development](https://oxarus.com/en/studio/services)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [idea to working product.](#hero)
- [product types.](#kinds)
- [from week one to launch.](#timeline)
- [it's your code.](#handover)
- [we do the same work for ourselves.](#proof)
- [let's build your product.](#cta)
## idea to working product.
_STUDIO · APPLICATION ENGINEERING_
We build the platform you'll open to your customers, together with its mobile app. First a clickable prototype, then the real product, then launch. Code and accounts are in your name from day one.
- [Tell us about your project](https://oxarus.com/en/studio/services#cta-heading) → `open_page(path="/studio/services", anchor="cta-heading")`
- [How we work](https://oxarus.com/en/studio/services#timeline) → `open_page(path="/studio/services", anchor="timeline")`
- Web, iOS and Android end to end
- Clickable prototype by week 3
- You own the source code
1. Prototype
2. Design
3. Live
_Representative interface data_ · Illustrative product screens.
**Today's deliveries**
- **tabTitle:** Dispatch · Routely
- **product:** Routely
Dashboard · Orders · Map · Drivers · Customers · Settings
- **date:** Tue, Sep 15
- **search:** Search orders, drivers or addresses
- **In transit:** 38
- **Delivered:** 96
- **Delay risk:** 3
- **Avg. delivery time:** 24 min
**Live map**
- Kadıköy
- Ataşehir
- Üsküdar
**Orders**
- 0
- **no:** #8841
- **customer:** Bluebell Pharmacy
- **area:** Kadıköy
- **driver:** Emre
- **status:** In transit
- 1
- **no:** #8840
- **customer:** Northside Market
- **area:** Ataşehir
- **driver:** Selin
- **status:** Delivered
- 2
- **no:** #8839
- **customer:** Hilltop Bakery
- **area:** Üsküdar
- **driver:** Can
- **status:** In transit
- 3
- **no:** #8838
- **customer:** Dot & Line Stationery
- **area:** Kadıköy
- **driver:** Emre
- **status:** Preparing
- 4
- **no:** #8837
- **customer:** Harbor Café
- **area:** Üsküdar
- **driver:** Can
- **status:** Delivered
- 5
- **no:** #8836
- **customer:** Parkview Optics
- **area:** Ataşehir
- **driver:** Selin
- **status:** Delay risk
- **transit:** In transit
- **delivered:** Delivered
- **preparing:** Preparing
- **risk:** Delay risk
**Fleet**
- **vehicles:** 24 vehicles
- **active:** 21 active
- **nav:** menu
- **kpis:** summary cards
- **Live map:** map + routes
- **Orders:** order list
- **top:** search and date
- **release:** Version 1.0 is live
- **releaseMeta:** App Store · Google Play · Web
- **time:** 14:26
- **hello:** Have a good shift, Emre
- **next:** Next delivery
- **customer:** Bluebell Pharmacy
- **address:** Moda Cad. No:18, Kadıköy
- **eta:** 6 min
- **stops:** 3 stops left
- **cta:** Mark delivered
- _14:41_
- **customer:** Hilltop Bakery
- **area:** Üsküdar
- _14:58_
- **customer:** Harbor Café
- **area:** Üsküdar
- **shift:** Shift · 12/15 deliveries
## product types.
_WHAT WE BUILD_
Most projects fit one of these four patterns. Knowing which one you're closest to helps us pin down scope faster in the first call.
- **Subscription platform** · _10–14 weeks_
If you want to offer your product to other businesses for a monthly fee.
- **EXAMPLE:** Appointment and shift scheduling software
**IN THE FIRST RELEASE**
- Company accounts and user roles
- Subscriptions and billing
- Admin panel and reports
**PLATFORMS**
Web · iOS · Android
**TYPICAL INTEGRATIONS**
- iyzico
- e-Invoice
- Google sign-in
- Slack
- _Representative interface data_
- role-based menu
- subscription plan
- revenue report
- **Marketplace** · _12–16 weeks_
If you're connecting buyers with sellers, or service providers with customers.
- **EXAMPLE:** An app connecting tradespeople with homeowners
**IN THE FIRST RELEASE**
- Two-sided sign-up and profiles
- Search, filters and reviews
- Payments and commission
**PLATFORMS**
Web · iOS · Android
**TYPICAL INTEGRATIONS**
- Marketplace payments
- SMS verification
- Maps
- Push notifications
- _Representative interface data_
- seller profile
- search and filters
- cart and commission
- **Booking and membership** · _8–12 weeks_
If your customers buy a spot, a time slot or a package.
- **EXAMPLE:** A membership app for a gym chain
**IN THE FIRST RELEASE**
- Calendar and availability
- Online payment and cancellation rules
- Reminders and loyalty
**PLATFORMS**
Web · iOS · Android
**TYPICAL INTEGRATIONS**
- Virtual POS
- Google Calendar
- WhatsApp reminders
- _Representative interface data_
- availability calendar
- payment and cancellation
- time slot and reminder
- **Field and mobile teams** · _10–14 weeks_
If your team works in the field and HQ needs to keep track of them.
- **EXAMPLE:** A work order app for technical service teams
**IN THE FIRST RELEASE**
- Task assignment and routing
- Photos, signatures and location
- Offline mode
**PLATFORMS**
iOS · Android · Web
**TYPICAL INTEGRATIONS**
- Maps and routing
- ERP sync
- Push notifications
- _Representative interface data_
- live route
- signature and photo
- offline tasks
- **IN THE FIRST RELEASE:** Point at an item to see where it sits on the wireframe.
**TIME TO FIRST RELEASE**
- **unit:** WEEKS
_Interface labels:_ First release
## from week one to launch.
_PROCESS_
A typical first release takes twelve weeks. Every phase ends with something you can see and try.
1. **Discovery**
Scope, user flows and a clear first-release list.
- Interviews
- User flows
- Release list
**TEAM**
- Product
- Design
2. **Clickable prototype**
A prototype you can click through on a phone or in a browser. You can show it to your customers.
- Wireframes
- Clickable prototype
- User testing
**TEAM**
- Design
- Product
3. **Interface design**
Every screen designed for your brand, plus a component library.
- Screen designs
- Component library
- Brand alignment
**TEAM**
- Design
4. **Development**
Two-week increments, each ending with new features in the preview environment.
- API and database
- Web and mobile screens
- Preview environment
**TEAM**
- Web
- Mobile
- Backend
5. **Testing and stores**
Testing on real devices, plus App Store and Google Play submissions.
- Device testing
- Store submission
**TEAM**
- QA
- Mobile
6. **Launch**
The product is in your users' hands. Monthly development continues from there.
- Go-live
- Monitoring
**TEAM**
- Product
- Mobile
- Backend
- **done:** done
- **active:** in progress
- **next:** up next
1. **Scope sign-off**
2. **Prototype demo**
3. **Beta**
4. **Launch**
- **play:** Play
- **pause:** Pause
- **replay:** Replay
- **jump:** Go to phase
- **next milestone:** Next
_Interface labels:_ Week · What this phase delivers · PROGRESS
## it's your code.
_HANDOVER_
You don't end up dependent on us. When the project wraps, you have everything you need to carry on with another team.
- **All of the source code**
In a repository under your account, with its full history.
- **Server and store accounts**
Cloud, App Store and Google Play accounts are opened in your company's name.
- **Design files**
Every screen and component, fully editable.
- **Setup and operations docs**
Clear enough for a new developer to get going in a day.
_Representative interface data_ · Representative repository
- **repo:** routely
_Representative interface data_ · Representative repository
- .github/
- workflows/
- apps/
- web/
- mobile/
- admin/
- packages/
- ui/
- api/
- infra/
- docs/
- setup.md
- architecture.md
- README.md
_Representative interface data_ · Representative repository
Code · History · CI/CD · Design · Docs
_Interface labels:_ Click an item to see where it lives in the repo.
## we do the same work for ourselves.
_OUR OWN PRODUCT_
Pals is the portal we build and run for educational institutions. It's used every day on web, iOS and Android. That's where we learned what it takes to ship a product and keep it running.
- Web, iOS and Android
- Flexible roles and permissions
- Active daily use
- [Explore Pals](https://oxarus.com/en/studio/pals) → `open_page(path="/studio/pals")`
> Live at EduNeta
_Representative interface data_
**Today's classes**
- **date:** Wed, Sep 16
- **Math · 9-A** · _09:00_
- **room:** B204
- **Physics · 10-C** · _10:30_
- **room:** Lab 2
- **Literature · 11-B** · _13:15_
- **room:** A108
- **attendance:** Attendance taken
## let's build your product.
_PROJECT_
Describe what you want to build in a few sentences. We'll come back with a clear first take on scope, timeline and budget.
- [Tell us about your project](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=App%20project) → `contact(subject="App project")`
## Actions
- [Tell us about your project](https://oxarus.com/en/studio/services#cta-heading) → `open_page(path="/studio/services", anchor="cta-heading")`
- [How we work](https://oxarus.com/en/studio/services#timeline) → `open_page(path="/studio/services", anchor="timeline")`
- [Explore Pals](https://oxarus.com/en/studio/pals) → `open_page(path="/studio/pals")`
- [Tell us about your project](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=App%20project) → `contact(subject="App project")`
- [Türkçe](https://oxarus.com/tr/studio/services) → `switch_locale(locale="tr", path="/studio/services")`
## Related pages
- [Oxarus Studio](https://oxarus.com/en/studio)
---
title: "Interactive design and UI/UX · Oxarus Studio"
description: "We design interfaces directly in code: real states, fluid transitions and a design system that grows with your product."
url: https://oxarus.com/en/studio/design
key: studio-design
route: /studio/design
unit: studio
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/studio/design
en: https://oxarus.com/en/studio/design
documents:
json: https://oxarus.com/machine/en/studio/design.json
jsonld: https://oxarus.com/machine/en/studio/design.jsonld
txt: https://oxarus.com/machine/en/studio/design.txt
schema: oxarus.machine/2.0
---
# Interactive design and UI/UX · Oxarus Studio
> We design interfaces directly in code: real states, fluid transitions and a design system that grows with your product.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Studio](https://oxarus.com/en/studio) › [Interactive Design](https://oxarus.com/en/studio/design)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [design, finished in code.](#hero)
- [touch it, feel it.](#play)
- [one button, two feels.](#feel)
- [decide once, apply everywhere.](#system)
- [make your product feel like this.](#cta)
## design, finished in code.
_STUDIO · INTERACTIVE DESIGN_
We build the interface as working components from the start, loading, error and success states included. Every press gets a visible response.
- [Tell us about your project](https://oxarus.com/en/studio/design#cta-heading) → `open_page(path="/studio/design", anchor="cta-heading")`
- [Try it yourself](https://oxarus.com/en/studio/design#play) → `open_page(path="/studio/design", anchor="play")`
- Design delivered as code
- Every state of every component
- A design system that grows with your product
1. Sketch
2. Code
3. Motion
_Representative interface data_ · Illustrative editor and preview.
- **file:** CheckoutButton.tsx
- **preview:** Preview
- **product:** Wireless headphones
- **price:** ₺4,990
- **idle:** Complete payment
- **loading:** Processing
- **success:** Paid
- 24
- 16
- 48
- **curve:** SPRING\_PRESS
- **stiffness:** stiffness
- **damping:** damping
- idle
- processing
- success
- **Subtotal:** ₺4,990
- **Shipping:** Free
- **totalLabel:** Total
- **spacing:** Spacing
- **a11y:** Accessibility
- **motion:** Motion
## touch it, feel it.
_PLAYGROUND_
The six pieces below actually work: hover, press, drag. Users usually notice that a product was made with care in moments this small.
- **Magnetic button**
**Get started**
- **Toggle**
- **Like**
**Like**
**Drag to reorder**
- Design review
- Client call
- Release notes
- Weekly report
- **Slider** · _people_
_Representative interface data_
- hover
- pressed
- focus
- active
_Interface labels:_ Move your cursor closer · Click · Notifications on · Notifications off · Press the heart · Move the rows · Drag · Copy · Click · OXARUS-2026 · Copied · Your invite code
## one button, two feels.
_FEEL_
Both scenes have the same add-to-cart button. On the left the motion is untuned, on the right it is tuned. Press the buttons, change the values and compare.
- **flat:** Untuned
- **tuned:** Tuned
- **stiffness:** Stiffness
- **damping:** Damping
_Representative interface data_
**Added to cart**
- **body:** Wireless headphones · ₺4,990
Snappy · Balanced · Bouncy · Gentle
- **curve:** Motion curve
- **overshoot:** Overshoot
- **settle:** Settle time
> Appears in a single frame
> Eases in and settles into place
- **add:** Add to cart
- **frames:** Frame by frame
_Representative interface data_
**Wireless headphones**
- **price:** ₺4,990
_Interface labels:_ Play · Reset to default
## decide once, apply everywhere.
_DESIGN SYSTEM_
Color, corner radius and density are each a variable. Change one and the whole product updates at once. Pick on the left, watch on the right.
- **accent:** Accent color
- **radius:** Corners
- **density:** Density
- Sharp
- Soft
- Round
- Comfortable
- Compact
_Representative interface data_
**Invite your team**
- **email:** Email address
- **placeholder:** Your teammate's email
- **role:** Role
- Admin
- Member
- **invite:** Send invite
- **badge:** 3 seats left
- **cancel:** Cancel
**Team members**
- **Deniz Arslan**
- **role:** Admin
- **Mert Kaya**
- **role:** Member
- **Ece Demir**
- **role:** Member
#### tokens.css
- Purple
- Sea green
- Terracotta
- Champagne
- Ink
**Button states**
- default
- hover
- pressed
- focus
- disabled
- **changed:** changed
_Interface labels:_ Copy · Copied · Reset to default
## make your product feel like this.
_DESIGN_
Tell us about your current interface or your new idea. We'll work out together where to start.
- [Tell us about your project](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Interface%20design) → `contact(subject="Interface design")`
## Actions
- [Tell us about your project](https://oxarus.com/en/studio/design#cta-heading) → `open_page(path="/studio/design", anchor="cta-heading")`
- [Try it yourself](https://oxarus.com/en/studio/design#play) → `open_page(path="/studio/design", anchor="play")`
- [Tell us about your project](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Interface%20design) → `contact(subject="Interface design")`
- [Türkçe](https://oxarus.com/tr/studio/design) → `switch_locale(locale="tr", path="/studio/design")`
## Related pages
- [Oxarus Studio](https://oxarus.com/en/studio)
---
title: "iOS and Android app development · Oxarus Studio"
description: "We build your iOS and Android apps end to end: apps that work offline, send notifications, use the device's camera and location, and stay solid in the stores."
url: https://oxarus.com/en/studio/mobile
key: studio-mobile
route: /studio/mobile
unit: studio
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/studio/mobile
en: https://oxarus.com/en/studio/mobile
documents:
json: https://oxarus.com/machine/en/studio/mobile.json
jsonld: https://oxarus.com/machine/en/studio/mobile.jsonld
txt: https://oxarus.com/machine/en/studio/mobile.txt
schema: oxarus.machine/2.0
---
# iOS and Android app development · Oxarus Studio
> We build your iOS and Android apps end to end: apps that work offline, send notifications, use the device's camera and location, and stay solid in the stores.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Studio](https://oxarus.com/en/studio) › [Mobile](https://oxarus.com/en/studio/mobile)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [in pockets, every day.](#hero)
- [everything the phone can do.](#native)
- [launch is part of the job.](#release)
- [keeping it running is on us.](#health)
- [one codebase or two apps?](#stack)
- [let's put your app in their pockets.](#cta)
## in pockets, every day.
_STUDIO · MOBILE_
End-to-end app development for iPhone and Android. They keep working when the connection drops and send notifications at the right moment, and we run the whole process from store review to launch.
- [Tell us about your app](https://oxarus.com/en/studio/mobile#cta-heading) → `open_page(path="/studio/mobile", anchor="cta-heading")`
- [What it can do](https://oxarus.com/en/studio/mobile#native) → `open_page(path="/studio/mobile", anchor="native")`
- iOS and Android at the same time
- Works offline
- App Store and Google Play submissions included
1. Two devices
2. Offline
3. Notification
_Representative interface data_ · Illustrative app screens.
- **brand:** Brewline
- **hello:** Good morning, Sophia
- **points:** 340 points
- **reward:** 2 more for a free coffee
- **menuTitle:** What are we drinking today?
- **Filter coffee**
- **price:** ₺85
> Ethiopia, V60
- **Oat latte**
- **price:** ₺120
> Double shot
- **Cold brew**
- **price:** ₺110
> 16 hours
- **order:** Place order
- **offline:** Offline
- **queued:** Order queued
- **queuedBody:** It'll send automatically once you're back online.
- **lockTime:** 08:42
- **lockDate:** Tuesday, September 15
**Your oat latte is ready**
- **app:** BREWLINE
- **body:** Moda branch · Pick it up at the counter
- **ago:** now
**Your order**
- **eta:** 2 min
1. Received
2. Preparing
3. Ready
- **store:** Moda branch · Order A-214
- **store:** Moda branch · 350 m
Hot · Iced · Sweets
- **light:** Cream theme
- **dark:** Dark theme
- **queueMeta:** 1 order · ₺120
- **retry:** Waiting for connection
**Your points were updated**
- **body:** +12 points · Total 352
- **ago:** 08:15
## everything the phone can do.
_DEVICE_
Apps do what websites can't. Pick one and see how it works on a phone.
- **Camera scanning**
Scans an invoice, ID or barcode and fills in the form for you.
- _Representative interface data_ · Illustrative screen
- **screen:** Place the barcode inside the frame
- _Representative interface data_ · Illustrative screen
- Barcode scanned
- Product · Oat milk 1 L
- Barcode · 8690000123457
- Stock · 24 units
- **Location**
Shows the nearest branch, the field team or a delivery on the map.
- _Representative interface data_ · Illustrative screen
- **screen:** Nearest to you: Moda branch · 350 m
- _Representative interface data_ · Illustrative screen
- Open · until 22:00
- 4 min · walk
- 3 · in line
- ₺120 · last order
- Get directions
- **Face ID and fingerprint**
Secure sign-in and payment approval without typing a password.
- _Representative interface data_ · Illustrative screen
- **screen:** Confirming with Face ID
- _Representative interface data_ · Illustrative screen
- No password needed
- Payee · Brewline Moda
- Amount · ₺240
- Approved · 0.4 s
- _Representative interface data_ · Illustrative screen
- **screenAndroid:** Confirming with fingerprint
- **Smart notifications**
To the right person, at the right time, without needless repeats.
- _Representative interface data_ · Illustrative screen
- **screen:** Your package arrives today between 14:00–16:00
- _Representative interface data_ · Illustrative screen
- **label:** Delivery
- _Representative interface data_ · Illustrative screen
- now
- Order
- Your order has shipped · 2 items
- 12 min
- Invoice
- Your September invoice is ready
- 1 h
- Tuesday, September 15
- **Offline mode**
Keeps recording in elevators, warehouses and construction sites, then syncs once the connection is back.
- _Representative interface data_ · Illustrative screen
- **screen:** 3 records waiting to sync
- _Representative interface data_ · Illustrative screen
- **label:** Offline
- _Representative interface data_ · Illustrative screen
- Field records
- Stock count · Block B · 09:12
- Delivery photo · Kadıköy · 09:20
- Fault note · Elevator 2 · 09:31
- Morning check · Synced · 08:40
- **Apple Pay and Google Pay**
One-tap payment without entering card details.
- _Representative interface data_ · Illustrative screen
- **screen:** ₺240 · Double-click to confirm
- _Representative interface data_ · Illustrative screen
- **label:** Brewline
- _Representative interface data_ · Illustrative screen
- Item · 2 × Oat latte
- Pickup · Moda branch
- _Representative interface data_ · Illustrative screen
- **screenAndroid:** ₺240 · Tap to confirm
_Interface labels:_ Platform
## launch is part of the job.
_STORES_
Test builds, store reviews, rejected submissions. We track all of it; you just see that the new version is live.
_Representative interface data_ · Representative
- **version:** 2.4.0
- _iPhone and iPad_
- **store:** App Store
1. Build
2. TestFlight
3. Apple review
4. Live
- _Representative interface data_ · Representative
- 14 min
- 35 min
- ~24 h
- next day
- _Phone and tablet_
- **store:** Google Play
1. Build
2. Closed testing
3. Google review
4. Live
- _Representative interface data_ · Representative
- 12 min
- 1 h
- ~6 h
- same day
Small fixes reach users the same day through in-app updates, without waiting on the stores.
_Representative interface data_ · Representative
- **waiting:** Waiting
- **running:** In progress
> Live
_Representative interface data_ · Representative
- **rollout:** Staged rollout
_Representative interface data_ · Representative
**release.log**
- _09:02_
- **tick:** 0
- **text:** Building 2.4.0 (318) · iOS and Android
- _09:11_
- **tick:** 0
- **text:** Automated tests passed, builds signed
- _09:16_
- **tick:** 1
- **text:** Uploaded to the Play closed testing track
- _09:18_
- **tick:** 1
- **text:** Release notes added · Turkish and English
- _09:51_
- **tick:** 2
- **text:** TestFlight · opened to 42 testers
- _10:05_
- **tick:** 2
- **text:** Submitted for review on both stores
- _15:20_
- **tick:** 3
- **text:** Google review approved
- _15:24_
- **tick:** 4
- **text:** Rolled out to 10% of Play users
- _+1d_
- **tick:** 5
- **text:** Apple review approved, live on the App Store
- _+1d_
- **tick:** 5
- **text:** Crash rate normal, Play rollout raised to 100%
- **ota tag:** 2.4.1 · same day
_Interface labels:_ Publish new version · Replay
## keeping it running is on us.
_AFTER LAUNCH_
After every release we check the same dashboard: is the app crashing, are users updating, what are the ratings saying?
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **crash:** Crash-free sessions
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **rating:** Store rating
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **ratingCount:** 2,184 ratings
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **adoption:** Version adoption
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- 0
- **v:** 2.4
- **p:** 78
- 1
- **v:** 2.3
- **p:** 18
- 2
- **v:** Other
- **p:** 4
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **startup:** Startup time
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **startupValue:** 0.9 s
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **board:** Brewline · live · v2.4.0
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
7 days · 30 days
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
86 · 8 · 3 · 1 · 2
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
> First 14 days after release
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- 0
- **platform:** iOS
- **p50:** 0.8
- **p90:** 1.3
- 1
- **platform:** Android
- **p50:** 1
- **p90:** 1.7
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **Daily sessions:** 18.4K
- **ANR rate:** 0.21%
- **API errors:** 0.08%
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
**Recent events**
- _09:40_
- **text:** 2.4.0 live on the App Store
- _08:12_
- **text:** Android rollout reached 100%
- _yesterday_
- **text:** Slow startup on older devices, fixed in 2.4.1
- _yesterday_
- **text:** Crash rate stayed below threshold
_Representative interface data_ · Illustrative values; the real dashboard is set up per project.
- **secondsUnit:** s
## one codebase or two apps?
_TECHNOLOGY_
There's no single right answer. We choose per project and tell you why up front.
- **Single codebase**
- **tech:** React Native · Expo
- **source:** Two apps from one source
**When it fits**
- When the app and web will evolve together
- When the first release needs to ship fast
- When most screens are lists, forms and content
> The right starting point for most business apps.
- Scanner.tsx
- app.json
- **Shared code**
85–95%
- **First release**
8–12 weeks
- **Device access**
Via modules
- **Workflow**
One workflow
- **Separate native apps**
- **tech:** Swift · Kotlin
- **source:** Each platform from its own source
**When it fits**
- When camera, audio or sensors are used heavily
- When widgets and watch apps matter
- When interaction is graphics-heavy or game-like
> For projects that need the deepest device access.
- ScanView.swift
- ScanActivity.kt
- **Shared code**
0–20%
- **First release**
14–20 weeks
- **Device access**
Full
- **Workflow**
iOS and Android apart
#### Build outputs
## let's put your app in their pockets.
_MOBILE_
Tell us what you want your users to do on their phones. Together we'll pin down which approach fits and what the first release covers.
- [Tell us about your app](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Mobile%20app) → `contact(subject="Mobile app")`
## Actions
- [Tell us about your app](https://oxarus.com/en/studio/mobile#cta-heading) → `open_page(path="/studio/mobile", anchor="cta-heading")`
- [What it can do](https://oxarus.com/en/studio/mobile#native) → `open_page(path="/studio/mobile", anchor="native")`
- [Tell us about your app](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Mobile%20app) → `contact(subject="Mobile app")`
- [Türkçe](https://oxarus.com/tr/studio/mobile) → `switch_locale(locale="tr", path="/studio/mobile")`
## Related pages
- [Oxarus Studio](https://oxarus.com/en/studio)
---
title: "Market engineering and research · Oxarus Quant"
description: "Oxarus Quant builds L.I.T., a market terminal, alongside custom trading robots, published research and institutional market infrastructure."
url: https://oxarus.com/en/quant
key: quant
route: /quant
unit: quant
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/quant
en: https://oxarus.com/en/quant
documents:
json: https://oxarus.com/machine/en/quant.json
jsonld: https://oxarus.com/machine/en/quant.jsonld
txt: https://oxarus.com/machine/en/quant.txt
schema: oxarus.machine/2.0
---
# Market engineering and research · Oxarus Quant
> Oxarus Quant builds L.I.T., a market terminal, alongside custom trading robots, published research and institutional market infrastructure.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Quant](https://oxarus.com/en/quant)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
- Not investment advice. Trading in financial markets carries a risk of losing capital.
## Sections
- [engineering for markets.](#hero)
- [four areas, one discipline.](#areas)
- [each area feeds the others.](#flow)
- [we have skin in the game.](#stance)
- [let's talk markets.](#cta)
## engineering for markets.
_OXARUS QUANT_
We build systems that run on our own capital. We also build the tools, research and infrastructure behind them for clients.
- [Get in touch](https://oxarus.com/en/quant#cta-heading) → `open_page(path="/quant", anchor="cta-heading")`
- [What we do](https://oxarus.com/en/quant#areas) → `open_page(path="/quant", anchor="areas")`
- Measure first, then decide
- Publish the ideas that fail, too
- Build the halt controls from day one
1. Terminal
2. Robots
3. Research
4. Engineering
- [L.I.T.](https://oxarus.com/en/quant/lit)
- [Custom robots](https://oxarus.com/en/quant/robots)
- [Research](https://oxarus.com/en/quant/research)
- [Engineering](https://oxarus.com/en/quant/engineering)
> Representative screen. Not investment advice.
_Interface labels:_ Explore
## four areas, one discipline.
_AREAS_
- **L.I.T.** · _Early access_
A terminal that brings news, the economic calendar and market data onto one screen.
- [L.I.T.](https://oxarus.com/en/quant/lit)
- **Custom trading robots** · _Service_
Describe your rules, and we'll write a MetaTrader 5 robot built for you alone.
- [Custom trading robots](https://oxarus.com/en/quant/robots)
- **Research** · _Published_
Measurements on levels, gaps and price behavior.
- [Research](https://oxarus.com/en/quant/research)
- **Engineering** · _Institutional_
Data pipelines, testing infrastructure and risk controls.
- [Engineering](https://oxarus.com/en/quant/engineering)
> Representative screens. Not investment advice.
_Interface labels:_ Explore
## each area feeds the others.
_LOOP_
The four areas may look like separate products, but they run on shared infrastructure. What research measures becomes a robot rule; a control built in engineering carries over unchanged to the terminal and the robots.
- Research
- Robots
- Engineering
- L.I.T.
_Representative interface data_
- level\_study.ipynb
- Robot.ex5
- pipeline · breakers
- terminal
Handoff
1. **A finding becomes a rule**
If a level's name doesn't change the odds of a break, no robot gets a rule that says 'open a trade at this level.' Only behavior that holds up against a control group makes it into a rule.
- **Proof:** Level families ~41%, control ~40%: no difference.
- _Representative interface data_
- **artifact:** level\_study.ipynb → rules.md
2. **A measurement becomes context**
We measured how long gaps take to close. The terminal shows this next to the news as context, never as a trade recommendation.
- **Proof:** 65% of gaps closed in the opening session, 95% within five trading days and 98% within 60 days.
- _Representative interface data_
- **artifact:** gap\_study → L.I.T. context panel
3. **Controls go inside the robot**
Daily loss limit, stale data and spread checks are added to every robot from the same module. Before a robot starts, the conditions under which it stops are already written down.
- **Proof:** The stop rule is written before the start rule.
- _Representative interface data_
- **artifact:** breakers.yaml → Robot.mq5
4. **Clean data, honest measurement**
Minute prices from two sources are compared, and gaps and synthetic ticks are filtered out. Research runs on this cleaned data.
- **Proof:** Minute data, 2020–2026, two pairs.
- _Representative interface data_
- **artifact:** feed\_diff → M1 dataset
5. **Live logs feed back into tests**
The robot's live logs are compared with a replay of the same day in the test environment. If the two diverge, the test infrastructure gets fixed first.
- **Proof:** Live and test must produce the same sequence of events.
- _Representative interface data_
- **artifact:** Experts journal → test suite
6. **The pipeline feeds the terminal**
News, calendar and price feeds pass through the same normalization pipeline. In the terminal, time, source and impact tag read consistently on every card.
- **Proof:** One pipeline, one time reference.
- _Representative interface data_
- **artifact:** news\_pipeline → Intelligence Wire
_Interface labels:_ Pick a handoff, or click an area in the diagram.
## we have skin in the game.
_STANCE_
We run the systems we build on our own capital first. Before we use an idea, we measure it and compare the result with a control group under the same conditions. We don't publish result figures; this page describes the method.
- **No control group, no finding** · _CONTROL_
Every measurement is compared against matched samples drawn at random under the same conditions. No difference means no finding.
_01_
- **An idea that fails on two pairs is shelved** · _REPLICATION_
A result on a single pair can be chance. It has to replicate on at least two independent pairs, across different years.
_02_
- **Tail-event days get their own inventory** · _INVENTORY_
Sudden gaps, liquidity pullbacks and surprise decisions are logged separately, so they don't disappear into the average.
_03_
- **The stop rule is written before the start rule** · _HALT_
Before a system goes live, the conditions under which it stops are defined in code and in documentation.
_04_
#### Gates an idea has to clear
## let's talk markets.
_QUANT_
Terminal, custom robot, research or infrastructure: tell us what you're working on, and we'll route you to the right team.
- [Get in touch](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
## Actions
- [Get in touch](https://oxarus.com/en/quant#cta-heading) → `open_page(path="/quant", anchor="cta-heading")`
- [What we do](https://oxarus.com/en/quant#areas) → `open_page(path="/quant", anchor="areas")`
- [Get in touch](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
- [Türkçe](https://oxarus.com/tr/quant) → `switch_locale(locale="tr", path="/quant")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
- [L.I.T.](https://oxarus.com/en/quant/lit)
- [Custom Robots](https://oxarus.com/en/quant/robots)
- [Research](https://oxarus.com/en/quant/research)
- [Engineering](https://oxarus.com/en/quant/engineering)
---
title: "L.I.T.: Forex news and market terminal · Oxarus Quant"
description: "News, the economic calendar, central banks, correlations and your portfolio in one terminal. Join the early access list for L.I.T."
url: https://oxarus.com/en/quant/lit
key: quant-lit
route: /quant/lit
unit: quant
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/quant/lit
en: https://oxarus.com/en/quant/lit
documents:
json: https://oxarus.com/machine/en/quant/lit.json
jsonld: https://oxarus.com/machine/en/quant/lit.jsonld
txt: https://oxarus.com/machine/en/quant/lit.txt
schema: oxarus.machine/2.0
---
# L.I.T.: Forex news and market terminal · Oxarus Quant
> News, the economic calendar, central banks, correlations and your portfolio in one terminal. Join the early access list for L.I.T.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Quant](https://oxarus.com/en/quant) › [L.I.T.](https://oxarus.com/en/quant/lit)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
- Not investment advice. Trading in financial markets carries a risk of losing capital.
- Part of the copy in this language is still identical to the source (Turkish) copy.
## Sections
- [markets, on one screen.](#hero)
- [market prep, in one place.](#modules)
- [beyond the headline.](#context)
- [be among the first users.](#waitlist)
## markets, on one screen.
_QUANT · L.I.T._
No more jumping between ten tabs. A headline lands and gets summarized, with the relevant pairs and linked calendar data right beside it.
- [Join early access](https://oxarus.com/en/quant/lit#waitlist) → `join_lit_waitlist()`
- [Modules](https://oxarus.com/en/quant/lit#modules) → `open_page(path="/quant/lit", anchor="modules")`
- News and calendar in one feed
- Short AI-assisted summaries
- Connects to your MetaTrader 5 account
1. News
2. Strength
3. Calendar
_Representative interface data_ · Representative screen. Not investment advice.
- **brand:** OXARUS LIT
- **brandSub:** LIVE INTELLIGENCE
- **user:** Trading Desk
- **userRole:** Executive Admin
- **clock:** 08:31:24
- **tz:** UTC+3
- **liveFeed:** LIVE FEED
| | | |
| --- | --- | --- |
| EUR/USD | 1.1537 | -0.02 |
| GBP/USD | 1.3456 | -0.20 |
| USD/JPY | 155.05 | +0.03 |
| XAU/USD | 2,412.8 | +1.66 |
| AUD/USD | 0.7132 | +0.08 |
| USD/CAD | 1.3939 | +0.14 |
| USD/CHF | 0.8190 | +0.10 |
| NZD/USD | 0.5762 | +0.09 |
**TERMINAL MODULES**
- Dashboard
- Intelligence Wire
- Macro Agenda
- Central Banks
- Strength Matrix
- Correlations
- Vault
- Live Charts
- Portfolio (MT5)
**Live Intelligence Wire**
- **sub:** Showing 24 of 277 reports · Synchronized to UTC+3
- **batch:** Batch AI Synthesis
- **search:** Search all reports (Fed, CPI)…
- **sync:** Auto-Sync: 15s
All Intelligence · Forex & Macro · Digital Assets · Corporate & M&A
- **Euro zone inflation beats forecasts as services prices climb** · _HIGH IMPACT_ · _4m ago_
- **src:** Reuters
- **body:** Headline inflation rose to 2.9% in August, above the 2.7% consensus, two days before the ECB meeting.
- **AUD/USD holds key support ahead of the FOMC** · _INTEL_ · _18m ago_
- **src:** Forexlive
- **body:** The pair is trading lower this week after breaking below a rising trendline.
- **BoE's Mann: wage growth still too strong for comfort** · _INTEL_ · _32m ago_
- **src:** Bloomberg
- **body:** External MPC member says persistence in services inflation argues for patience.
- **Oil steadies as traders weigh the OPEC+ supply outlook** · _INTEL_ · _41m ago_
- **src:** CNBC
- **body:** Brent held near its weekly range as markets awaited inventory data.
- **Japan exports rise for a third straight month** · _INTEL_ · _1h ago_
- **src:** Nikkei
- **body:** Shipments to Asia offset softer demand from Europe in the latest trade release.
- **US retail sales surprise to the upside in August** · _HIGH IMPACT_ · _1h ago_
- **src:** Reuters
- **body:** Control group sales rose 0.6%, twice the median estimate.
- **read:** Read & AI
**Currency Relative Strength Index**
- **sub:** Dynamic multi-pair aggregated strength algorithm (0 – 100)
- 1D
- 1W
- **synth:** AI Flow Synthesis
| | | | | | |
| --- | --- | --- | --- | --- | --- |
| NZD | New Zealand Dollar | 90 | ULTRA STRONG | RISING | +0.26 |
| AUD | Australian Dollar | 87 | ULTRA STRONG | RISING | +0.24 |
| EUR | Euro | 62 | BULLISH | STABLE | +0.05 |
| CHF | Swiss Franc | 54 | NEUTRAL | STABLE | -0.02 |
| USD | US Dollar | 51 | NEUTRAL | STABLE | -0.04 |
| CAD | Canadian Dollar | 49 | NEUTRAL | STABLE | -0.06 |
| JPY | Japanese Yen | 45 | NEUTRAL | STABLE | -0.09 |
| TRY | Turkish Lira | 38 | BEARISH | FALLING | -0.11 |
| GBP | British Pound | 15 | ULTRA WEAK | FALLING | -0.32 |
- **velocity:** Velocity
**Macroeconomic Agenda & Calendar**
- **catalyst:** HIGH IMPACT CATALYST
- **event:** FOMC Economic Projections
- **meta:** Target: DXY, EUR/USD, XAU/USD
- 02
- 08
- 57
HOURS · MINS · SECS
- **simulate:** Simulate Scenarios
- **sub:** Tracking 5 of 73 global releases · Timezone UTC+3
Today · Tomorrow · This Week · Next Week
- High Only
- Medium+
- All Events
- **Inflation Rate YoY** · _Sept 16, 09:00_
- **ccy:** GBP
- **actual:** 3.1
- **forecast:** 3.1
- **previous:** 2.9
- GBP/USD
- EUR/GBP
- GBP/JPY
- **Retail Sales MoM** · _Sept 16, 15:30_
- **ccy:** USD
- **actual:** 1.2
- **forecast:** 0.8
- **previous:** -0.5
- DXY
- EUR/USD
- XAU/USD
- **FOMC Economic Projections** · _Sept 16, 21:00_
- **ccy:** USD
- **actual:** Pending
- **forecast:** –
- **previous:** –
- DXY
- EUR/USD
- USD/JPY
- **Fed Interest Rate Decision** · _Sept 16, 21:00_
- **ccy:** USD
- **actual:** Pending
- **forecast:** 4.00
- **previous:** 3.75
- DXY
- EUR/USD
- XAU/USD
ACTUAL · FORECAST · PREVIOUS
## market prep, in one place.
_MODULES_
Every module is useful on its own. Used together, they connect.
- **News feed**
Headlines from your sources, tagged by currency and briefly summarized.
- **Economic calendar**
The day's and week's releases, with impact level and countdown.
- **Central banks**
Policy rates, upcoming meetings and the latest statements.
- **Correlation**
How the relationships between pairs shift over time.
- **Matrix**
Currencies' strength against one another, at a glance.
- **Portfolio**
Positions and total exposure in your MetaTrader 5 account.
- **Vault**
Your own notes, saved headlines and screenshots.
- **Notifications**
An alert on your phone when key data or a headline you follow drops.
- **Session hours**
When the Sydney, Tokyo, London and New York sessions are open, and where they overlap.
- **Volatility**
Each pair's average daily range, and how much of it has been used so far today.
## beyond the headline.
_CONTEXT_
A headline on its own says little. L.I.T. places a short summary, the relevant pairs and linked calendar data next to every headline. It doesn't call direction.
_Representative interface data_ · Representative screen. Not investment advice.
- **Euro area inflation comes in above expectations**
- **Summary:** Headline inflation beat expectations, and core inflation rose too. The data landed two days before the ECB meeting.
- **Linked on the calendar:** ECB rate decision · Thursday 12:15
**Related pairs**
- EURUSD
- EURGBP
- EURCHF
- **US jobs data comes in weak**
- **Summary:** November job growth came in below expectations, with wage growth flat. The prior month was revised down.
- **Linked on the calendar:** Fed Chair speech · Tuesday 18:00
**Related pairs**
- EURUSD
- USDJPY
- XAUUSD
- **Bank of Japan keeps its policy framework unchanged**
- **Summary:** Rates were left on hold. The statement's language on wages is more upbeat than in the previous text.
- **Linked on the calendar:** Japan CPI · Friday 01:30
**Related pairs**
- USDJPY
- EURJPY
- GBPJPY
## be among the first users.
_EARLY ACCESS_
L.I.T. is currently in closed beta. We send invitations to people on the list in the order they joined.
**Early access form**
- **name:** Full name
- **email:** Email
- **consent:** I agree that my personal data is processed, as described in the PDPL privacy notice, to manage the L.I.T. early access list and contact me about my invitation.
**What would you use most?**
News feed · Economic calendar · Correlation and matrix · MT5 portfolio
- [Join the list](https://oxarus.com/en/quant/lit#waitlist) → `join_lit_waitlist()`
- **message prefix:** L.I.T. early access request
> Representative screen. Not investment advice.
**When you join the list**
- **Invitations in join order**
Invitations go out in waves, based on when you joined the list.
- **Your feedback shapes the roadmap**
Requests from closed beta users set module priorities.
- **Every module unlocked**
During the beta, the news feed, calendar, matrix and MT5 portfolio are all available together.
**Access waves**
| | |
| --- | --- |
| Closed beta | In progress |
| Early access list | Open for sign-up |
| General availability | Planned |
_Interface labels:_ Sending · You're on the list. We'll email you when your invitation is ready. · Couldn't send. Please try again in a moment. · PDPL privacy notice · Please confirm to continue.
## Actions
- [Join early access](https://oxarus.com/en/quant/lit#waitlist) → `join_lit_waitlist()`
- [Modules](https://oxarus.com/en/quant/lit#modules) → `open_page(path="/quant/lit", anchor="modules")`
- [Türkçe](https://oxarus.com/tr/quant/lit) → `switch_locale(locale="tr", path="/quant/lit")`
## Related pages
- [Oxarus Quant](https://oxarus.com/en/quant)
---
title: "Custom MetaTrader 5 trading robot development · Oxarus Quant"
description: "Tell us how you enter, manage and exit a trade, and we'll write a robot, indicator or panel for MetaTrader 5 built for you alone."
url: https://oxarus.com/en/quant/robots
key: quant-robots
route: /quant/robots
unit: quant
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/quant/robots
en: https://oxarus.com/en/quant/robots
documents:
json: https://oxarus.com/machine/en/quant/robots.json
jsonld: https://oxarus.com/machine/en/quant/robots.jsonld
txt: https://oxarus.com/machine/en/quant/robots.txt
schema: oxarus.machine/2.0
---
# Custom MetaTrader 5 trading robot development · Oxarus Quant
> Tell us how you enter, manage and exit a trade, and we'll write a robot, indicator or panel for MetaTrader 5 built for you alone.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Quant](https://oxarus.com/en/quant) › [Custom Robots](https://oxarus.com/en/quant/robots)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
- Not investment advice. Trading in financial markets carries a risk of losing capital.
## Sections
- [your rules, run by a robot.](#hero)
- [just describe it.](#builder)
- [the robot's journey.](#journey)
- [beyond the robot.](#catalog)
- [what we do and don't.](#honest)
- [tell us about your method.](#cta)
## your rules, run by a robot.
_QUANT · CUSTOM ROBOTS_
Have a method you've been running by hand for years? Walk us through your entry, stop, trade management and exit rules. We'll write a MetaTrader 5 robot built for you alone.
- [Describe your strategy](https://oxarus.com/en/quant/robots#cta-heading) → `open_page(path="/quant/robots", anchor="cta-heading")`
- [How to describe it](https://oxarus.com/en/quant/robots#brief) → `open_page(path="/quant/robots", anchor="brief")`
- Your strategy, coded for you alone
- Specification first, code second
- We work under an NDA
1. Your rules
2. Code
3. On the chart
_Representative interface data_ · Representative screen. Not investment advice.
- **window:** MetaTrader 5
- **symbol:** EURUSD · H1
- **briefTitle:** Client notes
- _Entry_
- **text:** With price above the 50 EMA, buy when a green candle engulfs the red one.
- _Stop_
- **text:** Stop 5 pips below the last swing low.
- _Manage_
- **text:** Once 20 pips in favor, move the stop to break-even, then trail it 15 pips behind.
- _Risk_
- **text:** 1% of balance per trade. No new trades during news hours.
- **file:** ClientTrendPullback.mq5
- **running:** Robot running
- **entry:** Buy
- **sl:** Stop
- **be:** Break-even
- **trail:** Trailing stop
File · View · Insert · Charts · Tools · Window · Help
M1 · M5 · M15 · M30 · H1 · H4 · D1 · W1 · MN
- **algo:** Algo Trading
- Trade
- Exposure
- History
- Journal
- Experts
- **waiting:** Waiting for the approved specification…
- compiling ClientTrendPullback.mq5
- including RiskSizing.mqh, NewsWindow.mqh
- 0 errors, 0 warnings, 312 msec elapsed
- ClientTrendPullback (EURUSD,H1) initialized
- entry condition met: bullish engulfing above EMA(50)
- order #1042 buy 0.42 EURUSD at 1.08736, sl 1.08512
- position #1042 stop moved to break-even 1.08736
- position #1042 trailing stop 1.08921
## just describe it.
_SPECIFICATION_
No coding required. Pick your rules or add one in your own words; the robot's specification, its MetaTrader inputs and the test list update as you choose.
- **How should it enter a trade?**
- Moving average crossover
- Support / resistance breakout
- At a set time, on a set condition
- **How should the trade be managed?**
- Fixed stop and target
- Break-even, then trailing stop
- Partial take-profits
- **Position size?**
- Fixed lot
- Percent of balance
- **When should it stay out?**
- Around major news releases
- During the Asian session
- Friday evening
**Specification**
- A buy opens when the fast average crosses above the slow one; a sell opens when it crosses below.
- A buy opens when price closes above the highest high of the last 20 candles; a sell opens when it closes below the lowest low.
- At the set time, a single trade opens if the defined condition is met.
- Every trade opens with a fixed stop and a fixed target.
- Once price moves in favor, the stop moves to the entry level, then trails at a set distance.
- Part of the position closes at the first target, and the rest at the second.
- Every trade opens with the set fixed lot.
- Lot size is calculated from the stop distance so each trade risks the set percentage of balance.
- No new trades from 30 minutes before to 30 minutes after major news.
- No new trades during the Asian session.
- No new trades after 20:00 on Friday.
#### MetaTrader inputs
#### How the rules play out on the chart
- The conditions under which the robot enters
- How an open trade is protected and closed
- How much is risked on each trade
- Optional: times to stay out of the market
- **Your own rule** · _clarified on the call_
- **placeholder:** e.g. Close all trades at the Friday close
- **clear:** Clear
**Behavior tests**
- **state:** ready to test
_Interface labels:_ Specification completeness · updated · Optional: a rule the options don't cover
## the robot's journey.
_PROCESS_
We get your sign-off at the end of every step. No rule goes into the code unless we've agreed on it.
1. **Discovery call** · _NOTES_
We walk through your method together, using example trades on the chart.
- _Representative interface data_ · Representative
**What this step produces**
- **file:** call-notes.md
- _Method_
- **v:** Buy pullbacks to the 50 EMA in the trend direction
- _Example trades_
- **v:** Entries and exits marked on the chart
- _Open question_
- **v:** Is the stop measured from the last swing low or the last two?
- _Open question_
- **v:** Which calendar defines news hours?
2. **Specification** · _SIGN-OFF_
Every rule becomes a clear sentence, with nothing left ambiguous. You approve it.
- _Representative interface data_ · Representative
**What this step produces**
- **file:** SPEC-0142 · rev 04
- _§1 Entry_
- **v:** Buy on a bullish engulfing candle above the 50 EMA
- _§2 Stop_
- **v:** 5 pips below the last swing low
- _§3 Manage_
- **v:** Break-even after 20 pips, then a 15-pip trailing stop
- _§4 Risk_
- **v:** 1% of balance per trade; no new trades during news hours
- _Sign-off_
- **v:** Approved by the client
3. **Code** · _MQL5_
The robot is written in MQL5. Inputs come with names that make sense to you.
- _Representative interface data_ · Representative
**What this step produces**
- **file:** ClientTrendPullback.mq5
- _Compile_
- **v:** 0 errors, 0 warnings
- _Inputs_
- **v:** InpRiskPercent · InpEmaPeriod · InpStopBufferPips
- _Modules_
- **v:** RiskSizing.mqh · NewsWindow.mqh
- _Traceability_
- **v:** Every spec clause links to its place in the code
4. **Behavior test** · _TEST_
In the Strategy Tester, we verify trade by trade that the robot follows your rules exactly.
- _Representative interface data_ · Representative
**What this step produces**
- **file:** Strategy Tester · EURUSD,H1
- _§1 Entry_
- **v:** Entry condition verified on every trade
- _§2 Stop_
- **v:** Stop placed at the rule's level on every trade
- _§3 Manage_
- **v:** Break-even and trailing steps follow the rule
- _§4 News_
- **v:** No new trades opened inside the news window
5. **Delivery and setup** · _DELIVERY_
We deliver the compiled, licensed .ex5 file with setup notes. The scope of post-delivery fixes is set in the contract; source code comes under a separate agreement.
- _Representative interface data_ · Representative
**What this step produces**
- **file:** Delivery package
- _ClientTrendPullback.ex5_
- **v:** Compiled, licensed robot
- _Setup notes_
- **v:** What each input does and how to install
- _Test report_
- **v:** Rule checks from the Strategy Tester
- _Fix support_
- **v:** Scope agreed in the contract
- _ClientTrendPullback.mq5_
- **v:** Source code, under a separate agreement
The next step starts once you sign off.
_Interface labels:_ Previous step · Next step
## beyond the robot.
_WHAT WE BUILD_
Besides robots, we write indicators, scripts, panels and alert services, and port older robots to MT5. Pick a file.
- **Trading robot**
A robot that opens, manages and closes trades according to your rules.
- **folder:** Experts
- **file:** Robot.ex5
- **Example:** A robot that scales in on trend reversals
- **Inputs:** 14
- **Platform:** MT5
- **Delivery:** .ex5
- **kind:** Expert Advisor
- **Custom indicator**
An indicator that draws your own levels, zones or calculations on the chart.
- **folder:** Indicators
- **file:** Indicator.ex5
- **Example:** An indicator that plots the previous day's levels automatically
- **Inputs:** 8
- **Platform:** MT5
- **Delivery:** .ex5
- **kind:** Custom Indicator
- **One-off script**
Short tools you run once to get a specific job done.
- **folder:** Scripts
- **file:** Script.ex5
- **Example:** A script that closes every open trade in one click
- **Inputs:** 3
- **Platform:** MT5
- **Delivery:** .ex5
- **kind:** Script
- **Trading panel**
A panel that calculates lot size and sets stop and target by dragging them on the chart.
- **folder:** Experts
- **file:** Panel.ex5
- **Example:** A panel that sizes lots from a risk percentage
- **Inputs:** 11
- **Platform:** MT5
- **Delivery:** .ex5
- **kind:** Expert · Panel
- **Alerts and notifications**
Notifies you by phone, email or Telegram when a condition is met.
- **folder:** Services
- **file:** Alert.ex5
- **Example:** A service that messages Telegram when a level breaks
- **Inputs:** 6
- **Platform:** MT5
- **Delivery:** .ex5
- **kind:** Service
- **Migration and fixes**
We port your MetaTrader 4 robot to MT5, and fix robots that don't work.
- **folder:** Experts
- **file:** MT4\_to\_MT5
- **Example:** An MT5 version of a legacy MT4 robot
- **Inputs:** —
- **Platform:** MT4 → MT5
- **Delivery:** .ex5 + report
- **kind:** Port & fix
- **Delivery**
- **ex5:** Compiled, licensed .ex5
- **ex5 tag:** Default
- **mq5:** Source code (.mq5)
- **mq5 tag:** Separate agreement
## what we do and don't.
_STRAIGHT TALK_
**We do**
- Turn the strategy you describe into code, exactly
- Test that the robot follows the rules
- Keep your code and strategy confidential
- Provide fix support after delivery
**We don't**
- Suggest strategies or call market direction
- Promise profits
- Manage your account or touch your trades
- Sell the same robot to anyone else
**MQL5 seller profile**
We hold a verified seller account in the MQL5 community. A robot written for you is never listed on the Market; it is delivered to you alone.
- **Account:** Verified seller
- **Platform:** MetaTrader 5
- **Delivery:** Licensed .ex5
- **Source code:** By separate agreement
**Market · Seller profile**
- **handle:** MQL5 Market · Seller · Oxarus
##### Oxarus
- **monogram:** OX
_Verified seller_
- **platform:** MetaTrader 5
- **Experts**
- **code:** EA
- **Indicators**
- **code:** IND
- **Utilities**
- **code:** UTIL
- **file meta:** MT5 · .ex5
Licensed .ex5 · Source code by agreement · Custom work stays private
> Not investment advice. Trading in financial markets carries a risk of losing capital.
**We do**
- Each rule maps to code, point by point. Delivery is a compiled, licensed .ex5 file; source code comes under a separate agreement.
- A Strategy Tester report shows that every rule triggers correctly.
- An NDA is signed before any work begins.
- Bugs found after delivery are logged and fixed; the scope of that support is set in the contract.
**We don't**
- The strategy is yours; we only code the rules you define.
- No robot can know future outcomes, and we won't write anything that claims to.
- We never ask for your account details; you run the robot in your own terminal.
- A robot written for you is never sold to another client.
## tell us about your method.
_ROBOT_
Write out your rules in a few sentences and, if you can, attach screenshots of example trades. We'll pin down scope and timeline, then get back to you.
- [Describe your strategy](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Custom%20robot) → `contact(subject="Custom robot")`
## Actions
- [Describe your strategy](https://oxarus.com/en/quant/robots#cta-heading) → `open_page(path="/quant/robots", anchor="cta-heading")`
- [How to describe it](https://oxarus.com/en/quant/robots#brief) → `open_page(path="/quant/robots", anchor="brief")`
- [Describe your strategy](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Custom%20robot) → `contact(subject="Custom robot")`
- [Türkçe](https://oxarus.com/tr/quant/robots) → `switch_locale(locale="tr", path="/quant/robots")`
## Related pages
- [Oxarus Quant](https://oxarus.com/en/quant)
---
title: "Forex market structure research · Oxarus Quant"
description: "Studies on support and resistance levels, weekend gaps and how price behaves at levels, built on millions of minutes of data."
url: https://oxarus.com/en/quant/research
key: quant-research
route: /quant/research
unit: quant
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/quant/research
en: https://oxarus.com/en/quant/research
documents:
json: https://oxarus.com/machine/en/quant/research.json
jsonld: https://oxarus.com/machine/en/quant/research.jsonld
txt: https://oxarus.com/machine/en/quant/research.txt
schema: oxarus.machine/2.0
---
# Forex market structure research · Oxarus Quant
> Studies on support and resistance levels, weekend gaps and how price behaves at levels, built on millions of minutes of data.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Quant](https://oxarus.com/en/quant) › [Research](https://oxarus.com/en/quant/research)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
- Not investment advice. Trading in financial markets carries a risk of losing capital.
## Sections
- [we measure first.](#hero)
- [two published studies.](#studies)
- [how long at the level?](#dwell)
- [when do they close?](#gaps)
- [how we avoid fooling ourselves.](#method)
- [let data answer your question.](#cta)
## we measure first.
_QUANT · RESEARCH_
We test widely held but rarely measured market ideas against data: seven years of minute prices, a matched control group for every idea and a repeat on a second pair. We publish the ideas that don't hold up, too.
- [Institutional research](https://oxarus.com/en/quant/research#cta-heading) → `open_page(path="/quant/research", anchor="cta-heading")`
- [Findings](https://oxarus.com/en/quant/research#studies) → `open_page(path="/quant/research", anchor="studies")`
- Minute data, 2020–2026
- A matched control group in every test
- Replicated on EURUSD and GBPUSD
1. Level
2. Control
3. Result
_Representative interface data_ · Representative chart. Findings are for research purposes only and are not investment advice.
- **file:** level\_study.ipynb
- **dataset:** EURUSD · M1 · 2020–2026 · 40,658 touches
- **tag:** Representative chart
Count touches · Build control lines · Compare rates
- **done:** done
- **level:** Previous day high (PDH)
- **band:** band = 0.05 × ATR
- **levelTag:** PDH
**Matched control**
- **tag:** ctl
- **body:** For every real level, a line at the same distance that means nothing. Taken from another day's real offset, shifted by 7 days.
- **Real level:** 9–25 / day
- **Control line:** ~25 / day
- **Distance distribution:** identical
**Three touches on one level**
- 0
- **n:** #1
- **minutes:** 4
- **dwell:** 4 min
- **out:** REJECT
- 1
- **n:** #2
- **minutes:** 9
- **dwell:** 9 min
- **out:** REJECT
- 2
- **n:** #3
- **minutes:** 31
- **dwell:** 31 min
- **out:** BREAK
> The touch that stayed longest in the band broke the level. One representative day; the rates are in the third cell.
- **resultTitle:** Break rate · by level family
| | | |
| --- | --- | --- |
| PIVOT | 41 | 40 |
| PDHLC | 41 | 40 |
| ROUND | 41 | 40 |
| SWING | 41 | 40 |
| FIB | 39 | 39 |
**Same result every year**
- 2020
- 2021
- 2022
- 2023
- 2024
- 2025
- 2026
- **verdict:** No difference: a level's name doesn't change the odds of a break.
> Representative chart; rates are from the published study.
## two published studies.
_STUDIES_
Each study states its sample, period and control method. Pick a finding to bring its panel forward in the figure.
> From the published study. For research purposes only, not investment advice.
- **Do levels really hold?** · _EURUSD and GBPUSD · 2020–2026_
At pivots, previous-day levels, round numbers, swing and Fibonacci levels, we checked whether price broke through, and compared the results with meaningless control lines that share the same distance distribution.
- **sample:** 83,527
- **sample unit:** touches
**STUDY FACTS**
- **Sample:** 83,527 touches
- **Period:** 2020–2026
- **Pairs:** EURUSD · GBPUSD
- **Resolution:** M1 (minute bars)
- **Control:** Distance-matched lines
- **Replication:** Replicated on GBPUSD
**FINDINGS**
- Every level family broke about 41% of the time; matched control lines, 40%. The same held in each of the seven years.
- Which touch it was made no difference: from the 1st touch to the 5th, 41%, 40%, 39%, 42%, 44%.
- The only thing that changed the outcome was how long price stayed near the level on that touch. The same result replicated point for point on GBPUSD.
- Break rate by level family
- Break rate by touch number
- Break probability by time in the band
- **Go to the dwell-time chart**
- [Go to the dwell-time chart](https://oxarus.com/en/#dwell)
- **Do weekend gaps close?** · _EURUSD · weekend and holiday breaks_
We measured when the Monday opening gap made it back to Friday's close, and how far price traveled before it did.
- **sample:** 345
- **sample unit:** breaks
**STUDY FACTS**
- **Sample:** 345 breaks
- **Period:** 2020–2026
- **Pair:** EURUSD
- **Resolution:** M1 (minute bars)
- **Reference:** Friday close
- **Horizon:** 60 days
**FINDINGS**
- 65% of gaps closed during the opening session; among those, the median time to close was 11 minutes.
- 95% closed within five trading days, and 98% within sixty days.
- The small tail that never closed lined up exactly with geopolitical shock days. For gaps larger than 5 pips, the median excursion before closing was 21 pips, and 120 pips in the worst decile.
- Closed in the opening session
- Share closed over time
- Excursion before the close
- **Go to the gap chart**
- [Go to the gap chart](https://oxarus.com/en/#gaps)
| | | |
| --- | --- | --- |
| PIVOT | 41 | 40 |
| PDHLC | 41 | 40 |
| ROUND | 41 | 40 |
| SWING | 41 | 40 |
| FIB | 39 | 39 |
- **matched control:** 40
**touch number**
41 · 40 · 39 · 42 · 44
- 20
- 21
- 22
- 23
- 24
- 25
- 26
**stops**
0 · 10 · 30 · 60
**eurusd**
41 · 51 · 55 · 56
**gbpusd**
40 · – · 54 · –
- **all:** 65
- **big:** 10
- **median time to close:** 11 min
- **open**
- **all:** 0
- **big:** 0
- **session**
- **all:** 65
- **big:** 10
- **5 days**
- **all:** 95
- **big:** 85
- **60 days**
- **all:** 98
- **p50:** 21
- **p90:** 120
- **max:** 470
- **still open after 60 days:** 2
_Interface labels:_ Research note · Published · Figure {n} · level · 2020–2026: same every year · {value} pts · min · pips · all gaps · over 20 pips · log scale
## how long at the level?
_TIME AT THE LEVEL_
The longer price stays in a level's band, the more likely it is to break the level, until the effect levels off. Pick a duration; the chart and the ranges update together.
- **stop option:** ≥{minutes} min
- **replication:** GBPUSD replication
- **probability:** break probability
- **base:** base
- **lift:** vs base
- **lift unit:** pts
- **not measured:** not measured
- **pair eur:** EURUSD
- **pair gbp:** GBPUSD
> Break probability by time spent in the level band. A research finding, not a trade recommendation.
#### By session: base → 30 minutes
#### Time in the band
- **rejects:** Rejections
- **breaks:** Breaks
- **median:** median
- **selected:** selected
**Robustness to band width**
With the band varied between 0.03 and 0.08 × ATR, the 30-minute lift stayed between +12 and +14 points.
- **plateau:** plateau
- **dataset:** EURUSD · GBPUSD · M1 · 2020–2026 · n=83,527
**Time already in the band**
0 · 10 · 30 · 60
**eurusd**
41 · 51 · 55 · 56
**gbpusd**
40 · – · 54 · –
- **control:** 40
- **control short:** control
**plateau**
56 · 57
- **minute unit:** min
- **break query:** P(break | dwell ≥ {minutes} min)
- **chart sample:** EURUSD n=40,658 · GBPUSD n=42,869
**By session: base → 30 minutes**
- **ASIA**
- **base:** 43
- **at30:** 55
- **LDN**
- **base:** 40
- **at30:** 56
- **NY**
- **base:** 40
- **at30:** 55
- **By session: base → 30 minutes:** 30 min
**rejects**
9 · 10
**breaks**
28 · 31
- 0.03
- 0.05
- 0.08
- **Robustness to band width:** × ATR
**Robustness to band width**
12 · 14
- **Robustness to band width:** 30 min
## when do they close?
_WEEKEND GAPS_
Across 345 weekend and holiday breaks, how long the opening gap took to get back to Friday's close. Pick a horizon.
**Horizon**
- **Session**
- **5 days**
- **60 days**
The remaining 2%: gaps still open after sixty days. Every one of them coincides with a major geopolitical shock.
#### Cumulative share of gaps closed
#### By gap size
- **all gaps:** All gaps
- **big gaps:** Over 20 pips
- **same session:** Closed in the same session
- **within week:** Within 5 trading days
**Excursion before closing (≥5 pips)**
Before the gap closed, price moved the other way by a median of 21 pips, 120 pips in the worst decile, and 470 pips at most.
- **median fill:** median fill
- **axis open:** open
- **axis session:** session
- **axis day:** 1 day
- **axis week:** 5 days
- **axis two months:** 60 days
- **unfilled:** unfilled
- **not measured:** not measured
- **pips unit:** pips
> EURUSD, 345 weekend and holiday breaks. A research finding, not investment advice.
- **n:** 345
- **median fill:** 11 min
- **Horizon:** 60 days
- **chart sample:** EURUSD n=345
**points**
0 · 65 · – · 95 · 98
- 0
- **at:** 1
- **value:** 10
- 1
- **at:** 3
- **value:** 85
- **unfilled:** 2
- **all:** 65
- **big:** 10
- **all:** 95
- **big:** 85
- **all:** 98
**Excursion before closing (≥5 pips)**
- **p50:** 21
- **p90:** 120
- **max:** 470
- **Excursion before closing (≥5 pips):** pips · log scale
## how we avoid fooling ourselves.
_METHOD_
We logged every interim result that turned out wrong. Switch any entry between how it looked at first and what it actually was.
- **Random lines broke less often than levels, so levels looked like 'magnets.'** · _CONTROL BIAS_
The random lines sat farther from price. Once the control lines were built with the same distance distribution, the difference vanished.
- **Three months of data showed a clear dip at the third touch.** · _MULTIPLE COMPARISONS_
Across seven years of data, it evaporated. Run enough comparisons, and some differences show up by chance.
- **One measurement came out with a 100% break rate.** · _SIGN BUG_
When a rate sticks to 0 or 1, suspect the measuring machinery first. It was a single sign error.
- **An idea seemed to hold on one pair.** · _REPLICATION_
We rebuilt the same test from scratch on another pair. Nothing that failed to hold on both counted as a finding.
#### Correction log
- **resolved:** resolved
- **count:** {fixed} / {total} resolved
- **schematic:** schematic
- **show traps:** Show first glance
- **show fixes:** Apply corrections
- **random:** random lines
- **matched:** matched lines
- **levels:** levels
- **distance:** distance to price
**touch rates**
41 · 40 · 39 · 42 · 44
- **3 months of data**
7 years of data
- **bug: sign(dist):** 100
- **fixed:** 41
- **matched control:** 40
- **eur:** EUR 55
- **gbp:** GBP 54
- **start:** 0m
- **end:** 30m
_Interface labels:_ At first glance · Actually · open
## let data answer your question.
_RESEARCH_
If you'd like us to run measurements or hypothesis tests on market data for your organization, or build its research infrastructure, get in touch.
- [Send a research request](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Research%20request) → `contact(subject="Research request")`
## Actions
- [Institutional research](https://oxarus.com/en/quant/research#cta-heading) → `open_page(path="/quant/research", anchor="cta-heading")`
- [Findings](https://oxarus.com/en/quant/research#studies) → `open_page(path="/quant/research", anchor="studies")`
- [Send a research request](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Research%20request) → `contact(subject="Research request")`
- [Türkçe](https://oxarus.com/tr/quant/research) → `switch_locale(locale="tr", path="/quant/research")`
## Related pages
- [Oxarus Quant](https://oxarus.com/en/quant)
---
title: "Backtesting, data pipelines and risk controls · Oxarus Quant"
description: "Pipelines that clean market data, tests purged of look-ahead bias and risk controls that protect live systems. We build them for institutions, too."
url: https://oxarus.com/en/quant/engineering
key: quant-engineering
route: /quant/engineering
unit: quant
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/quant/engineering
en: https://oxarus.com/en/quant/engineering
documents:
json: https://oxarus.com/machine/en/quant/engineering.json
jsonld: https://oxarus.com/machine/en/quant/engineering.jsonld
txt: https://oxarus.com/machine/en/quant/engineering.txt
schema: oxarus.machine/2.0
---
# Backtesting, data pipelines and risk controls · Oxarus Quant
> Pipelines that clean market data, tests purged of look-ahead bias and risk controls that protect live systems. We build them for institutions, too.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Quant](https://oxarus.com/en/quant) › [Engineering](https://oxarus.com/en/quant/engineering)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
- Not investment advice. Trading in financial markets carries a risk of losing capital.
## Sections
- [from data to live.](#hero)
- [where backtests go wrong.](#pitfalls)
- [two sources, minute by minute.](#feeds)
- [five checks before every order.](#breakers)
- [we build it for you, too.](#services)
- [let's build your infrastructure.](#cta)
## from data to live.
_QUANT · ENGINEERING_
Building systems that trade our own capital taught us what belongs in the infrastructure: pipelines that verify data, tests closed to look-ahead bias and risk controls that halt a live system when they have to.
- [Institutional project](https://oxarus.com/en/quant/engineering#cta-heading) → `open_page(path="/quant/engineering", anchor="cta-heading")`
- [Risk controls](https://oxarus.com/en/quant/engineering#breakers) → `open_page(path="/quant/engineering", anchor="breakers")`
- Tests guarded against look-ahead bias
- Verified against two independent data sources
- Automatic circuit breakers in production
1. Data
2. Test
3. Live
_Representative interface data_ · Representative flow diagram.
- **file:** research-to-live
- **tag:** Representative flow
- **data:** Data
- **test:** Test
> Live
**Broker data**
- **detail:** EURUSD · M1
**Reference data**
- **detail:** independent second source
**Clean and compare**
- **detail:** median diff 0.20 pip
**Features**
- **detail:** previous bar only
**Backtest**
- **detail:** hourly spread distribution
**Walk-forward**
- **detail:** unseen period
**Risk gate**
- **detail:** 5 checks before every order
**Live**
- **detail:** order flow
**Monitoring**
- **detail:** event log and alerts
- **bars:** 2.4M minutes
- **delta:** median diff 0.20 pip
- **lookahead:** look-ahead: 0
- **breakers:** 5 circuit breakers armed
## where backtests go wrong.
_TESTING_
Most systems that look good on historical data are feeding on a flaw in the test itself. Pick one to see the flawed test, the corrected pipeline and the automated checks side by side.
- **Look-ahead**
- **Flawed test:** The day's close leaks into an intraday decision.
- **Corrected pipeline:** The read window ends before the current bar; anything after it is out of reach.
A value that's only known at the end of the day gets used during the day.
Every calculation draws only on the previous bar and earlier. We don't leave this to code review: by design, the data access layer can't see the future.
- **Synthetic ticks**
- **Flawed test:** A four-point synthetic path fills at prices that never traded.
- **Corrected pipeline:** The real tick path: every fill rests on a price that was actually seen.
Fake price paths generated from minute bars create fills that never happened.
We rerun critical results on real tick data and a second feed source.
- **Overfitting**
- **Flawed test:** One bright cell: results fall apart at neighboring settings.
- **Corrected pipeline:** A broad, stable region: the chosen setting's neighbors hold up too.
The best of hundreds of parameter combinations is picked and assumed to stay the best.
We choose parameters in one period and test them in a period they've never seen. Settings that don't hold at neighboring values are discarded.
- **Survivorship**
- **Flawed test:** A universe built from today's list never sees delisted instruments.
- **Corrected pipeline:** Every instrument trading on that date, including those removed later.
The test only uses instruments that still exist today.
The test universe is built from instruments that were actually available on that date.
- **Unrealistic costs**
- **Flawed test:** A fixed spread every hour: no session differences, no news widening.
- **Corrected pipeline:** Spread distribution by hour, with spikes around news preserved.
Spread, commission and slippage are assumed to be zero or fixed.
We use the real spread distribution by hour and session, including widening around news.
**Audit suite**
- **count:** {passed} / {total} passed
> If any audit is red, the change does not merge into the main branch.
- **run all:** Run all
- **queued:** queued
- **passed:** passed
- **pass:** pass
- **fail:** fail
- **representative:** Representative output
_Interface labels:_ Symptom · How we catch it · Automated checks · running
## two sources, minute by minute.
_DATA_
We compare the broker feed against an independent reference source, minute by minute. 1,721 shared trading days, 2.4 million shared minutes.
- **Median:** 0.2
- **90th percentile:** 0.4
- **99th percentile:** 1.8
- **Largest difference:** 16.8
- **unit:** pip
Most of the time, the difference is a fifth of a pip. That's why we can verify our results without depending on any single broker's data.
- **overlay:** Same minutes, two sources
- **histogram:** Distribution of minute-close differences
> The shape of the distribution is representative; the marked percentiles and the largest difference are measured.
- **histogram sample:** n = 2.4M · square-root scale
- **source a:** Broker
- **source b:** Reference
- **Shared trading days:** 1,721
- **Shared minutes:** 2.4million
- **Daily range difference, median:** 0.2pip
- **representative:** Representative path
- **measured:** measured
- **jump max:** Jump to the largest gap
- **validated:** validated
_Interface labels:_ Minute
## five checks before every order.
_RISK_
Every order the live system sends passes these checks. Trip one, then send a test order to see which check stops it.
- **Daily loss limit**
Intraday loss has hit the limit
No new trades open, open trades close according to the rules, and the system stays locked until the end of the day.
- **Spread guard**
Spread has widened to 4× normal
Pending orders are suspended, and no entries are made until the spread normalizes.
- **News window**
High-impact release within 10 minutes
No new trades open during the window, and stops are not widened.
- **Connection loss**
Server unresponsive for 20 seconds
No orders are sent until the connection is restored; on reconnect, positions are reconciled with the server.
- **Exposure cap**
Total risk in one currency is at the cap
No new positions involving that currency are opened.
- **status:** System status
- **representative:** Representative screen
**Test order**
Send an order through the gate and see which check passes and which one stops it.
- **send:** Send test order
- **accepted:** Order accepted
- **rejected:** Order rejected · {name}
- **accepted count:** accepted
- **blocked count:** blocked
_Interface labels:_ Trip · Reset · Armed · Tripped · Order flow open · Order flow halted · Re-arming controls · Running checks
## we build it for you, too.
_INSTITUTIONAL_
We build the infrastructure we run our own research and live systems on around your organization's data and processes.
- **Data pipelines**
Infrastructure that collects, cleans and stores price and news data from multiple sources.
**Tools used**
Python · Polars · Parquet · PostgreSQL
**DELIVERABLES**
- Source connectors and scheduled pulls
- Dual-source comparison and quality report
- Versioned, queryable data store
- **Testing infrastructure**
An environment where your team can test strategies free of look-ahead bias.
**Tools used**
Python · NumPy · pytest · Docker
**DELIVERABLES**
- Look-ahead-safe data access layer
- Walk-forward and parameter robustness reports
- Reproducible, containerized test environment
- **MetaTrader 5 tooling**
Robots, panels, bridges and reporting tools built for institutional use.
**Tools used**
MQL5 · C++ · MetaTrader 5 · REST
**DELIVERABLES**
- Robot, panel and indicator development
- Bridges between MetaTrader 5 and external systems
- Source code and setup documentation
- **Risk and monitoring dashboards**
Dashboards that show account exposure, limits and system health on a single screen.
**Tools used**
TypeScript · Next.js · WebSocket · PostgreSQL
**DELIVERABLES**
- Per-account exposure and limit view
- Circuit breaker states and event log
- Instant alerts on threshold breaches
- **representative:** Representative
## let's build your infrastructure.
_ENGINEERING_
Tell us what you need, whether it's a data pipeline, a test environment or a risk dashboard, and we'll define the scope and approach together.
- [Send a project request](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Institutional%20quant%20project) → `contact(subject="Institutional quant project")`
## Actions
- [Institutional project](https://oxarus.com/en/quant/engineering#cta-heading) → `open_page(path="/quant/engineering", anchor="cta-heading")`
- [Risk controls](https://oxarus.com/en/quant/engineering#breakers) → `open_page(path="/quant/engineering", anchor="breakers")`
- [Send a project request](https://oxarus.com/en/contact?start=quant) → `start_project_brief(topic="quant")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=Institutional%20quant%20project) → `contact(subject="Institutional quant project")`
- [Türkçe](https://oxarus.com/tr/quant/engineering) → `switch_locale(locale="tr", path="/quant/engineering")`
## Related pages
- [Oxarus Quant](https://oxarus.com/en/quant)
---
title: "Agentic hyperautomation · Oxarus Agent AI"
description: "AI agents that run multi-step processes across email, ERP, CRM, e-commerce and support channels, with approval steps, permissions and an audit trail."
url: https://oxarus.com/en/automation
key: automation
route: /automation
unit: automation
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/automation
en: https://oxarus.com/en/automation
documents:
json: https://oxarus.com/machine/en/automation.json
jsonld: https://oxarus.com/machine/en/automation.jsonld
txt: https://oxarus.com/machine/en/automation.txt
schema: oxarus.machine/2.0
---
# Agentic hyperautomation · Oxarus Agent AI
> AI agents that run multi-step processes across email, ERP, CRM, e-commerce and support channels, with approval steps, permissions and an audit trail.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Agent AI](https://oxarus.com/en/automation)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [agents that run processes end to end.](#hero)
- [when rules break, work goes on.](#shift)
- [pick a process, watch the agent.](#processes)
- [the agent works, you stay in control.](#control)
- [we measure first, then we scale.](#delivery)
- [questions about agents.](#faq)
- [let's pick your first process.](#cta)
## agents that run processes end to end.
_OXARUS AGENT AI_
Our AI agents read the email, find the record in your ERP, catch the mismatch, ask for approval where it's needed and close out the work. You step in only where a decision is required.
- [Describe your process](https://oxarus.com/en/automation#cta-heading) → `open_page(path="/automation", anchor="cta-heading")`
- [See the processes](https://oxarus.com/en/automation#processes) → `open_page(path="/automation", anchor="processes")`
- Runs on top of the tools you already use
- Human approval at critical steps
- Every action in the audit trail
1. Incoming email
2. Document and ERP
3. Check
4. Human approval
5. Record and notify
_Representative interface data_ · Representative agent console: a supplier invoice processed from email to ERP entry.
- **run:** run\_4821 · supplier invoice
- **tag:** Representative
- **running:** running
- **waiting:** awaiting approval
- **done:** completed
1. **Read the email**
- **detail:** Found a PDF invoice attached to the message from Northfield Supply.
2. **Parsed the invoice**
- **detail:** Extracted line items, quantities, tax and the total amount.
3. **Matched it to the PO**
- **detail:** Pulled PO-7710 from the ERP and compared the line items one by one.
4. **Flagged a price variance**
- **detail:** The unit price on NS-4410 is higher than on the PO; the variance breaks the tolerance rule.
5. **Requested approval**
- **detail:** Sent the finance lead an approval request with a summary of the variance, then waited.
6. **Posted the entry**
- **detail:** After approval, posted entry AP-5518 to the ERP.
7. **Notified the team**
- **detail:** Posted a summary and a link to the audit log in #ap-ops.
- **call:** tool call
- **result:** result
- **reason:** Reasoning
- **pending:** pending
- **back:** Back to the live step
- **hint:** Click a completed step to see its call and result.
**Incoming invoice**
- **supplier:** Supplier
- **po:** PO
- **lines:** Item
- **qty:** Qty
- **invoicePrice:** Invoice
- **poPrice:** PO
- **mismatch:** NS-4410 unit price is {percent} above the PO · tolerance {tolerance}
**Approval step**
- **approver:** Clara Wendt
- **role:** Finance lead
- **summary:** Variance {total}: {qty} units × {diff}
- **idle:** Queued
- **waiting:** Awaiting decision
- **approved:** Approved
- **elapsed:** elapsed
- **tools:** tool calls
- **human:** incl. human approval
## when rules break, work goes on.
_FROM AUTOMATION TO HYPERAUTOMATION_
Classic automation follows pre-written rules; when something unexpected happens, it stops and drops the work into a queue. An agent reads the situation, gathers context and decides what to do within set boundaries.
- **SAME EXCEPTION:** The supplier sent the invoice as a scanned PDF. The invoice has no PO number; it only appears in the body of the email. And one line item's price differs from the PO.
_Representative interface data_ · Representative
**Incoming email**
- **from:** Northfield Supply · Accounts
- **subject:** Invoice INV-20931
- **body:** Hello, the attached invoice belongs to your order {po}. Kind regards.
- **attachment:** INV-20931.pdf · scanned
_Representative interface data_ · Representative
**Scanned invoice**
- **po:** PO number
- **missing:** none
- **textLayer:** No text layer
_Representative interface data_ · Representative
- **play:** Play
- **pause:** Pause
- **replay:** Restart
- **step:** Step {n}
_Representative interface data_ · Representative
- **running:** running
- **stopped:** stopped
- **queued:** waiting in queue
- **waiting:** awaiting approval
- **done:** completed
- **Rule-based flow** · _RPA_
1. **Attachment downloaded**
PDF saved to a folder.
ok
2. **PO number field unreadable**
The template field is empty; the scanned document has no text layer.
fail
3. **Matching skipped**
The rule can't continue without a PO number.
fail
4. **Dropped into the error queue**
Waiting until someone notices.
warn
Result: the flow stopped, and the work has to be done by hand.
- **Agent** · _Agent AI_
1. **Read the document**
Extracted line items and amounts from the scanned PDF.
ok
2. **Found the missing data**
Pulled the PO number from the email body: PO-7710.
ok
3. **Spotted the variance**
NS-4410 has a price variance outside tolerance.
warn
4. **Sent it for approval**
Summarized the variance, checked with the authorized approver and posted the entry once approved.
ok
Result: work closed, the decision stayed with a human, every step logged.
- **Ambiguous input**
- **RULE-BASED:** Stops on documents outside the template
- **AGENT:** Reads the document and fills gaps from context
- **Exceptions**
- **RULE-BASED:** Every exception needs a new rule
- **AGENT:** Decides within policy, and asks when outside it
- **Cross-tool work**
- **RULE-BASED:** One trigger, one action
- **AGENT:** Works step by step across multiple systems
- **Change**
- **RULE-BASED:** Breaks when the screen changes
- **AGENT:** Works through APIs and authorized tools
- **Traceability**
- **RULE-BASED:** Often just an error log
- **AGENT:** Every decision logged with its reasoning
_Interface labels:_ TOPIC
## pick a process, watch the agent.
_PROCESSES_
The flows below are examples we build often. In each one the agent moves step by step across the systems your company uses, stops at the step that needs approval and waits for your decision.
- **human tag:** human approval
_Representative interface data_ · Representative
- **calls:** calls: {count}
_Representative interface data_ · Representative
- **skipped:** skipped
_Representative interface data_ · Representative
- **summary:** tool calls: {calls} · human decisions: {decisions} · all in the audit log
_Representative interface data_ · Representative
- **running:** running
- **waiting:** awaiting approval
- **done:** completed
- **rejected:** rejected
_Representative interface data_ · Representative
**Your approval is needed**
- **hint:** The agent stopped at this step. It continues based on your decision.
- **approve:** Approve
- **reject:** Reject
- **approved:** Approved by {role}
- **rejected:** Rejected by {role}
- **Invoice matching**
- **approver:** Finance lead
A supplier invoice arrived in the accounting inbox.
Invoice matched to the PO, entry posted, team notified.
No entry posted. The agent passed the variance to purchasing to raise with the supplier.
1. 0
Recognized the invoice attachment and the sending supplier.
2. 1
Extracted line items, tax and totals from the PDF.
3. 2
Ran a three-way match against the PO and delivery note.
4. 3
Sent the out-of-tolerance price variance for approval.
5. 4
Posted the approved invoice as an accounting entry.
6. 5
Posted a summary and the entry link in the finance channel.
- **Orders and returns**
- **approver:** Customer service manager
A customer opened a return request in the store.
Return eligibility checked, warehouse and customer informed.
No refund issued. The request went to customer service with the reasoning attached.
1. 0
Read the order, delivery date and return reason.
2. 1
Checked eligibility against the return policy.
3. 2
Created a return receipt and shipping code in the warehouse.
4. 3
Sent the high-value return for refund approval.
5. 4
After approval, posted the credit note and stock movement.
6. 5
Sent the customer the shipping code and next steps on WhatsApp.
- **Support triage**
- **approver:** Support team lead
A new request arrived in the support channel.
Request classified, simple ones answered, critical ones with the right person.
No assignment made. The request waits in the team lead's queue with its summary.
1. 0
Read the request; identified topic, language and urgency.
2. 1
Pulled the customer record and past requests.
3. 2
Checked the status of the related order.
4. 3
Sent the ready reply to the customer asking about order status.
5. 4
Asked for approval to route the complaint to the priority queue.
6. 5
Added a conversation summary to the customer record.
- **Lead qualification**
- **approver:** Sales rep
A quote request form came in from the website.
Lead scored, ready in the CRM, meetings offered to qualified leads.
No reply sent. The draft went back to the rep with a note to revise.
1. 0
Read the form answers and company details.
2. 1
Searched the CRM for an existing record and past conversations.
3. 2
Scored the lead against the agreed criteria.
4. 3
Submitted a personalized first reply draft for approval.
5. 4
Offered open slots from the sales rep's calendar.
6. 5
Logged the opportunity at the right stage with its owner.
- **Hiring and onboarding**
- **approver:** IT manager
A new hire's contract was signed.
Accounts ready, equipment request open, first-week plan shared.
Admin access not granted. The request went back to the IT manager with its reasoning.
1. 0
Pulled the employee record, department and start date.
2. 1
Prepared the role-based list of accounts and permissions.
3. 2
Submitted access that needs admin rights for approval.
4. 3
Opened the approved accounts and raised the equipment request.
5. 4
Emailed the new hire a welcome note and first-week plan.
6. 5
Announced the new hire and start date to the team.
_Interface labels:_ Replay · CONNECTED SYSTEMS · AGENT TRACE · TRIGGER · OUTCOME
## the agent works, you stay in control.
_CONTROL AND SECURITY_
Every agent runs with defined permissions, limits and approval steps. What it did, why it did it and who approved it are all on record, and a single click stops it when needed.
_Representative interface data_ · Representative
- **panelTitle:** Agent control panel · Northfield Supply
_Representative interface data_ · Representative
- **hint:** Change a setting: the verdicts on pending actions and the audit log update right away.
_Representative interface data_ · Representative
**Approval steps**
- **Out-of-tolerance invoice**
- **detail:** Price variance above {tolerance}
- **approver:** Finance lead
- **Amount above limit**
- **detail:** Payments and refunds over the per-transaction limit
- **approver:** Manager
- **First customer reply**
- **detail:** First message sent with a new template
- **approver:** Support lead
_Representative interface data_ · Representative
**Role permissions**
- read
- write
- pay
- 0
- **role:** invoice-agent
✓ · ✓ · ✗
- 1
- **role:** support-agent
✓ · ✓ · ✓
- 2
- **role:** sales-agent
✓ · ✗ · ✗
- **hint:** Click a box: the permission changes right away and is logged.
_Representative interface data_ · Representative
**Action limits**
- **Per-transaction amount**
- **currency:** EUR
- **Actions per hour** · _actions_
- **Retries on the same job** · _times_
- **usage:** {used} actions in the last hour
_Representative interface data_ · Representative
**Pending actions**
- 0
- **action:** Post invoice INV-20944 to the ERP
- **detail:** Baltic Freight · price variance {variance}
- 1
- **action:** Refund return R-1182
- **detail:** Order SO-10482
- 2
- **action:** Refund return R-1190
- **detail:** Bulk order SO-10477
- 3
- **action:** Update the opportunity stage in the CRM
- **detail:** Kestrel Labs · quote sent
- 4
- **action:** Send the first reply to the customer
- **detail:** Request T-3310 · new template
- 5
- **action:** Retry entry AP-5521
- **detail:** ERP timeout · attempt {retry}
- **auto:** Automatic
- **approval:** Goes to approval · {approver}
- **permission:** Blocked · no permission
- **limit:** Blocked · amount limit
- **retry:** Blocked · retry limit
- **throttled:** Queued · hourly limit
- **paused:** Stopped
- **auto:** {count} automatic
- **approval:** {count} in approval
- **blocked:** {count} blocked
_Representative interface data_ · Representative
**Audit log**
All · Agent · Human
- **empty:** No entries for this filter.
- 0
- **actor:** invoice-agent
- **action:** Entry AP-5518 posted to the ERP · approved by Clara Wendt
- 1
- **actor:** clara.wendt
- **action:** INV-20931 price variance approved
- 2
- **actor:** support-agent
- **action:** Request #3304 routed to the priority queue · reason: complaint
- 3
- **actor:** sales-agent
- **action:** No write permission; CRM update suggested to the rep
- **gateOn:** Approval step turned on: {rule}
- **gateOff:** Approval step turned off: {rule}
- **grant:** “{action}” permission granted to {role}
- **revoke:** “{action}” permission removed from {role}
- **limit:** {label}: {from} → {to}
- **stop:** All agents stopped
- **resume:** Agents restarted
_Representative interface data_ · Representative
**Emergency stop**
- **body:** Stops all agents immediately. Unfinished work is saved and waits until it's resumed.
- **stop:** Stop all agents
- **resume:** Restart agents
- **stopped:** All agents stopped
> {count} agents running
- **held:** {count} jobs waiting in the queue
- **running:** running
- **paused:** stopped
- **Human approval**
You decide which steps are critical; the agent stops there and asks.
- **Least privilege**
Each agent accesses only the systems and actions its job requires.
- **Audit log**
Every tool call, input, decision and approval is stored with a timestamp.
- **Limits**
When amount, volume or retry limits are hit, the agent stops.
- **Emergency stop**
One button stops every agent, and no work is lost.
## we measure first, then we scale.
_HOW WE WORK_
We start with a single process. We measure the result in a pilot, then widen the scope and the agent's permissions step by step once your team is ready.
- **weeks:** Week
1. **Discovery** · _1–2 weeks_
We talk with your teams and map the repetitive processes that involve rules and exceptions. Together we choose which ones suit an agent.
**DELIVERED IN THIS PHASE**
- Process inventory and prioritization
- Systems and data access list
- Success criteria
- _Representative interface data_ · Representative
**Process inventory**
- Process
- Frequency
- Exceptions
- Assessment
- **Invoice matching**
- **frequency:** Daily
- **exceptions:** Frequent
- **fit:** Pilot candidate
- **Return approval**
- **frequency:** Daily
- **exceptions:** Moderate
- **fit:** Next step
- **Lead qualification**
- **frequency:** Weekly
- **exceptions:** Few
- **fit:** Next step
- **Budget planning**
- **frequency:** Yearly
- **exceptions:** Many
- **fit:** Not a fit
- **picked:** Chosen for the pilot: {name}
2. **Process map** · _1 week_
We map the chosen process step by step: which system, which decision, which exception, and where human approval sits.
**DELIVERED IN THIS PHASE**
- End-to-end flow and exception map
- Approval steps and permission model
- Baseline measurement
- _Representative interface data_ · Representative
**Flow and exception map**
- Email arrived
- Document read
- Matched to PO
- Tolerance check
- Human approval
- ERP entry
- **gate:** approval step
- **exception:** Exception: no PO number on the invoice → taken from the email body
- **toggle:** Show the exception path
3. **Pilot agent** · _3–6 weeks_
We connect the agent to your real systems and run it first in observation mode, then with limited permissions.
**DELIVERED IN THIS PHASE**
- Working pilot agent
- Control panel and audit log
- Test and exception scenarios
- _Representative interface data_ · Representative
**Pilot mode**
- Observation mode
- Limited permissions
- Post entry AP-5519 to the ERP
- Reconciliation email to the supplier
- Payment instruction for INV-20950
- **suggested:** Suggested, not applied
- **applied:** Applied
- **approval:** Sent for approval
- **blocked:** Outside permissions, not done
4. **Measured rollout** · _ongoing_
We track results against the criteria set in the pilot and raise volume and permissions gradually as trust builds.
**DELIVERED IN THIS PHASE**
- Measurement dashboard
- Staged permission plan
- New process proposals
- _Representative interface data_ · Representative
**Permission levels**
- **Observation**
- **body:** The agent reads and suggests; it changes no records.
- **Approved actions**
- **body:** Every action is applied with a person's approval.
- **Limited authority**
- **body:** Work within limits runs on its own; anything outside goes to approval.
- **Next process**
- **body:** The next process is added with the same controls.
- **current:** now
- **raise:** Go up a level
- **lower:** Step back
5. **Handover and operations** · _ongoing_
We teach your team to run the agent. If you prefer, we keep handling monitoring, updates and new processes.
**DELIVERED IN THIS PHASE**
- Operations guide and training
- Monitoring and alerting setup
- Maintenance and development support
- _Representative interface data_ · Representative
**Monitoring and alerts**
- 0
- **when:** An approval waits longer than 4 hours
- **then:** The owner gets a reminder
- 1
- **when:** The same error happens 3 times in a row
- **then:** The agent stops, the team is alerted
- 2
- **when:** A new type of exception appears
- **then:** The job is set aside for review
- **report:** Weekly agent report
- **reportDetail:** Every Monday in the team channel
- **on:** on
- **off:** off
## questions about agents.
_FAQ_
How agents are kept in check, which systems they work with and how a pilot starts.
> **Let's look at your process**
>
> Discovery call
>
> If your question isn't answered here, write to us. We can go through the details of your process together.
> - [Send an email](mailto:info@oxarus.com) → `contact()`
**Question:** What happens if the agent makes a wrong decision?
**Answer:** The agent acts only within the permissions and limits you define. It asks for approval at critical steps and stops to ask when a case falls outside the policy. Every decision is logged with its reasoning, and all agents can be stopped with a single button.
**Question:** Do we need to replace our existing systems?
**Answer:** No. Agents work on top of your email, ERP, CRM, e-commerce, document and support channels, through APIs and authorized tools.
**Question:** How is this different from classic automation (RPA)?
**Answer:** A rule-based flow stops on a non-template document or an unexpected exception and drops the work into a queue. An agent reads the document, fills gaps from context and decides within policy; when a case is outside the policy, it asks.
**Question:** Which processes suit an agent?
**Answer:** Repetitive processes that involve rules and exceptions and move across several systems. In discovery we map your processes with your teams and choose the right one together.
**Question:** How does a pilot start, and how long does it take?
**Answer:** Discovery takes 1–2 weeks, the process map 1 week and the pilot agent 3–6 weeks. The pilot agent runs first in observation mode, then with limited permissions; permissions grow gradually against the criteria set in the pilot.
**Question:** Can our own team run the agent?
**Answer:** Yes. In the handover phase we teach your team to run the agent. If you prefer, we keep handling monitoring, updates and new processes.
## let's pick your first process.
_LET'S START_
Tell us about the process your team spends the most time on. We'll assess together whether it's a fit for an agent, and what kind of pilot it could start with.
- [Describe your process](https://oxarus.com/en/contact?start=automation) → `start_project_brief(topic="automation")`
## Actions
- [Describe your process](https://oxarus.com/en/automation#cta-heading) → `open_page(path="/automation", anchor="cta-heading")`
- [See the processes](https://oxarus.com/en/automation#processes) → `open_page(path="/automation", anchor="processes")`
- [Send an email](mailto:info@oxarus.com) → `contact()`
- [Describe your process](https://oxarus.com/en/contact?start=automation) → `start_project_brief(topic="automation")`
- [Türkçe](https://oxarus.com/tr/automation) → `switch_locale(locale="tr", path="/automation")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "Showcase: some of the brands Oxarus works with"
description: "Websites, systems, apps and AI agents we built for Cove 1907, Nata Holding, Vega Center, Palazzo İncek and other brands."
url: https://oxarus.com/en/showcase
key: showcase
route: /showcase
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/showcase
en: https://oxarus.com/en/showcase
documents:
json: https://oxarus.com/machine/en/showcase.json
jsonld: https://oxarus.com/machine/en/showcase.jsonld
txt: https://oxarus.com/machine/en/showcase.txt
schema: oxarus.machine/2.0
---
# Showcase: some of the brands Oxarus works with
> Websites, systems, apps and AI agents we built for Cove 1907, Nata Holding, Vega Center, Palazzo İncek and other brands.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Showcase](https://oxarus.com/en/showcase)
## Notices
- Projects and example results marked as placeholders shape the page layout; they are not real client work.
## Sections
- [some of our work.](#hero)
- [Some of the brands we've worked with](#wall)
- [Let's add your brand here](#cta)
## some of our work.
_SHOWCASE_
Corporate websites, CRM and ERP systems, mobile apps and AI agents. Click a brand to see what we built for it.
- **Brands:** 15
- **Sectors:** 8
- **Units:** 4
- **projects:** Brands
- **sectors:** Sectors
- **units:** Units
- **featured:** Featured projects
_Interface labels:_ Previous project · Next project · Pause autoplay · Start autoplay · View project · {current} / {total}
## Some of the brands we've worked with
_BRANDS_
Brands from real estate, retail, manufacturing, sports, education and logistics. Hover over a card to bring out the brand's own colors.
- **brands:** Brands
- **Cove 1907** · _Hub_
Website for Cove 1907, on the Güllük Gulf in Milas, Muğla. Nata Holding is developing the project in collaboration with Fenerbahçe Sports Club, with a marina and 1,907 living units, from one-bedroom flats to seven-bedroom villas.
- **Unit:** Hub
- **Sector:** Real estate
- **Platform:** Web
- **Year:** 2026
- [Open project](https://oxarus.com/en/showcase?p=cove-1907#brands) → `view_project(slug="cove-1907")`
- **Fenerbahçe** · _Hub_
Fenerbahçe Sports Club is the collaboration partner of the Cove 1907 project.
- **Unit:** Hub
- **Sector:** Sports
- **Platform:** Web
- **Year:** 2026
- [Open project](https://oxarus.com/en/showcase?p=fenerbahce#brands) → `view_project(slug="fenerbahce")`
- **Nata Holding** · _Hub_
A group of companies in construction, infrastructure, energy, mining and real estate. We built Nata Holding's website, CRM and ERP.
- **Unit:** Hub
- **Sector:** Business group
- **Platform:** Web
- [Open project](https://oxarus.com/en/showcase?p=nata-holding#brands) → `view_project(slug="nata-holding")`
- **Vega Center** · _Hub_
Website for Vega Center in Çankaya, Ankara. The Nata Yaşam project has 339 offices in three office blocks and an open-air shopping center.
- **Unit:** Hub
- **Sector:** Real estate
- **Platform:** Web
- **Year:** 2026
- [Open project](https://oxarus.com/en/showcase?p=vega-center#brands) → `view_project(slug="vega-center")`
- **Nata Vega** · _Hub_
Website for Nata Vega Outlet in Mamak, Ankara. The Nata Holding shopping center has more than 195 brands, cinemas and the AquaVega tunnel aquarium.
- **Unit:** Hub
- **Sector:** Retail
- **Platform:** Web
- **Year:** 2026
- [Open project](https://oxarus.com/en/showcase?p=nata-vega#brands) → `view_project(slug="nata-vega")`
- **Palazzo İncek** · _Hub_
Website for Palazzo İncek, a residential project of 11 detached villas in İncek, Ankara. Each villa has three floors and its own garden.
- **Unit:** Hub
- **Sector:** Real estate
- **Platform:** Web
- **Year:** 2026
- [Open project](https://oxarus.com/en/showcase?p=palazzo-incek#brands) → `view_project(slug="palazzo-incek")`
- **Modifuse** · _Hub_
Website for Modifuse, an Istanbul company making end-use parts with SLS additive manufacturing. It produces parts for defense, aerospace, automotive, medical devices and robotics.
- **Unit:** Hub
- **Sector:** Manufacturing
- **Platform:** Web
- **Year:** 2026
- [Open project](https://oxarus.com/en/showcase?p=modifuse#brands) → `view_project(slug="modifuse")`
- **Başer Grup** · _Hub_
Website for Başer Grup, an Ankara group working in automotive, insurance, vehicle conversion and energy since 1985. Its brands include a Ford dealership, Başer Sigorta and the B-Force charging network.
- **Unit:** Hub
- **Sector:** Business group
- **Platform:** Web
- **Year:** 2026
- [Open project](https://oxarus.com/en/showcase?p=baser-grup#brands) → `view_project(slug="baser-grup")`
- **Pals** · _Studio_ · _Live_
Our product that brings timetables, homework, exams, attendance and payments for schools into one app. Students, parents, teachers and administrators see the same information on their own screens; it is live at EduNeta.
- **Unit:** Studio
- **Sector:** Education
- **Platform:** iOS, Android, Web
- [Open project](https://oxarus.com/en/showcase?p=pals#brands) → `view_project(slug="pals")`
- **Skydagger** · _Agent AI_
An AI agent we built for Skydagger.
- **Unit:** Agent AI
- [Open project](https://oxarus.com/en/showcase?p=skydagger#brands) → `view_project(slug="skydagger")`
- **Routely** · _Studio_
A route planning and order tracking app for delivery teams. The operations team uses the web dashboard; drivers use the Android app.
- **Unit:** Studio
- **Sector:** Logistics
- **Platform:** Web, Android
- [Open project](https://oxarus.com/en/showcase?p=routely#brands) → `view_project(slug="routely")`
- **Orbit Freight** · _Hub_
A portal where a logistics company's customers track shipment status, documents and invoices.
- **Unit:** Hub
- **Sector:** Logistics
- **Platform:** Web
- [Open project](https://oxarus.com/en/showcase?p=orbit-freight#brands) → `view_project(slug="orbit-freight")`
- **Northfield Supply** · _Agent AI_
An AI agent that reads orders a wholesale supply team receives by email and PDF and enters them into the ERP. Records it isn't sure about go to a person for approval.
- **Unit:** Agent AI
- **Sector:** Logistics
- [Open project](https://oxarus.com/en/showcase?p=northfield-supply#brands) → `view_project(slug="northfield-supply")`
- **Redline Tutoring** · _Agent AI_
An assistant that answers questions a tutoring center receives on WhatsApp and schedules trial lessons.
- **Unit:** Agent AI
- **Sector:** Education
- [Open project](https://oxarus.com/en/showcase?p=redline-tutoring#brands) → `view_project(slug="redline-tutoring")`
- **Atlas Research Lab** · _Quant_
Data infrastructure that collects and cleans market data for a research team and makes it queryable.
- **Unit:** Quant
- **Sector:** Finance
- [Open project](https://oxarus.com/en/showcase?p=atlas-research#brands) → `view_project(slug="atlas-research")`
_Interface labels:_ Open project · Close · Previous · Next · Project · {current} / {total}
## Let's add your brand here
_NEXT PROJECT_
Tell us in a few sentences what you want to build. We'll work out together which unit takes it on and what the roadmap looks like.
- [Let's talk about your project](mailto:info@oxarus.com?subject=Showcase) → `contact(subject="Showcase")`
## Actions
- [Let's talk about your project](mailto:info@oxarus.com?subject=Showcase) → `contact(subject="Showcase")`
- [Türkçe](https://oxarus.com/tr/showcase) → `switch_locale(locale="tr", path="/showcase")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "Careers: Open roles at Oxarus"
description: "Open roles across Hub, Studio, Quant and Agent AI, and how hiring works. On-site and hybrid roles in Ankara or Istanbul; remote roles from anywhere."
url: https://oxarus.com/en/careers
key: careers
route: /careers
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/careers
en: https://oxarus.com/en/careers
documents:
json: https://oxarus.com/machine/en/careers.json
jsonld: https://oxarus.com/machine/en/careers.jsonld
txt: https://oxarus.com/machine/en/careers.txt
schema: oxarus.machine/2.0
---
# Careers: Open roles at Oxarus
> Open roles across Hub, Studio, Quant and Agent AI, and how hiring works. On-site and hybrid roles in Ankara or Istanbul; remote roles from anywhere.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Careers](https://oxarus.com/en/careers)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [Open roles](#hero)
- [All roles](#roles)
- [From application to offer](#process)
- [For everyone on the team](#benefits)
- [Don't see your role listed?](#cta)
## Open roles
_CAREERS_
We're hiring across Hub, Studio, Quant and Agent AI. On-site and hybrid roles are based in Ankara or Istanbul; remote roles have no city requirement.
- [View roles](https://oxarus.com/en/careers#roles) → `open_page(path="/careers", anchor="roles")`
- [Hiring process](https://oxarus.com/en/careers#process) → `open_page(path="/careers", anchor="process")`
- **locations:** Offices
_Representative interface data_
**oxarus / workspace**
- **review:** Code review
- **design:** Design review
- **release:** Release
- **lanes:** Units
- **hub:** Order sync
- **studio:** Pals attendance
- **quant:** L.I.T. news feed
- **agent:** Invoice agent evaluation
- **online:** Online
**feat(sync): incremental order cursor**
- _14:08_
- **author:** Burak Ş.
- **text:** On the first sync store.cursor is null, so since isn't sent and the API returns only the last 50 orders. Older orders never arrive.
- _14:31_
- **author:** Deniz A.
- **text:** You're right, I missed that. With no cursor it now falls back to a full sync, and there's a test for it.
- **approve:** Burak approved
- lint
- typecheck
- test
**Pals / Attendance screen**
- **status:** Resolved
- **before:** Before
> After
- _10:42_
- **author:** Elif K.
- **text:** Brought the row height down from 56 to 48. You now see 13 students on screen instead of 11.
- _10:55_
- **author:** Mert A.
- **text:** True, but the “Absent” button shrank too. I tapped the student below twice on my phone. Keep rows at 48 and make the button 44?
- _11:08_
- **author:** Elif K.
- **text:** OK, the button is 44 now. Also, a class with no students showed a blank screen, so I added a short line there.
- **decision:** Decision: rows 48, button 44. The empty-class text goes out in this week's release.
**L.I.T. / news feed service**
- **badge:** Live
1. **#219 merged to main** · _Selin Y. · 09:12_
2. **Ran overnight on staging, no missed headlines** · _09:40_
3. **Rollback command tried on staging** · _Can D. · 09:52_
4. **Deployed to production** · _Can D. · 10:05_
5. **Watching latency and error rate** · _now_
- **chart:** p95 latency · last hour
- **deploy:** release
- **status:** 185 ms before the release, 180 ms now. No new errors logged.
- **pause:** Pause autoplay
- **play:** Start autoplay
- **review:** Code
- **design:** Design
- **release:** Release
**Offices**
- **Ankara:** Engineering & R&D
- **Istanbul:** Operations & Architecture
## All roles
_ROLES_
Filter by unit, city or work model. To apply, upload your CV as a PDF.
- **role column:** Role
- **Senior Frontend Engineer** · _Hub_
Build fast, accessible corporate websites, AI search interfaces and e-commerce storefronts.
- **Unit:** Hub
- **City:** Ankara
- **Work model:** Hybrid
- **Level:** Senior
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=senior-frontend-engineer#roles) → `view_role(slug="senior-frontend-engineer")`
- [Apply](https://oxarus.com/en/careers?apply=senior-frontend-engineer#roles) → `apply_role(slug="senior-frontend-engineer")`
- **Backend Engineer** · _Hub_
Write and run the APIs, integrations and order flows behind client systems.
- **Unit:** Hub
- **City:** Istanbul
- **Work model:** Hybrid
- **Level:** Mid-level
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=backend-engineer#roles) → `view_role(slug="backend-engineer")`
- [Apply](https://oxarus.com/en/careers?apply=backend-engineer#roles) → `apply_role(slug="backend-engineer")`
- **Mobile Engineer (React Native)** · _Studio_
Build Pals and client apps for iOS and Android, including offline use.
- **Unit:** Studio
- **City:** Anywhere
- **Work model:** Remote
- **Level:** Mid-level
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=mobile-engineer-react-native#roles) → `view_role(slug="mobile-engineer-react-native")`
- [Apply](https://oxarus.com/en/careers?apply=mobile-engineer-react-native#roles) → `apply_role(slug="mobile-engineer-react-native")`
- **Product Designer** · _Studio_
Design screen flows for Pals and client apps, from research to prototype.
- **Unit:** Studio
- **City:** Istanbul
- **Work model:** Hybrid
- **Level:** Senior
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=product-designer#roles) → `view_role(slug="product-designer")`
- [Apply](https://oxarus.com/en/careers?apply=product-designer#roles) → `apply_role(slug="product-designer")`
- **Quant Developer (MQL5 / Python)** · _Quant_
Build the research tools behind the L.I.T. terminal and custom MT5 robots for clients.
- **Unit:** Quant
- **City:** Istanbul
- **Work model:** On-site
- **Level:** Senior
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=quant-developer#roles) → `view_role(slug="quant-developer")`
- [Apply](https://oxarus.com/en/careers?apply=quant-developer#roles) → `apply_role(slug="quant-developer")`
- **Data Engineer** · _Quant_
Build the market data pipelines behind Quant research and keep the data queryable.
- **Unit:** Quant
- **City:** Ankara
- **Work model:** Hybrid
- **Level:** Mid-level
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=data-engineer#roles) → `view_role(slug="data-engineer")`
- [Apply](https://oxarus.com/en/careers?apply=data-engineer#roles) → `apply_role(slug="data-engineer")`
- **AI Agent Engineer** · _Agent AI_
Build agents that handle documents, invoices and support work for Agent AI clients, with human approval.
- **Unit:** Agent AI
- **City:** Anywhere
- **Work model:** Remote
- **Level:** Senior
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=ai-agent-engineer#roles) → `view_role(slug="ai-agent-engineer")`
- [Apply](https://oxarus.com/en/careers?apply=ai-agent-engineer#roles) → `apply_role(slug="ai-agent-engineer")`
- **Engineering Internship** · _Oxarus_
Work with a mentor at our Istanbul office on changes that ship to production.
- **Unit:** Oxarus
- **City:** Istanbul
- **Work model:** On-site
- **Level:** Intern
> The application form asks for your name, email and CV as a PDF (up to 4 MB).
- [View details](https://oxarus.com/en/careers?role=engineering-internship#roles) → `view_role(slug="engineering-internship")`
- [Apply](https://oxarus.com/en/careers?apply=engineering-internship#roles) → `apply_role(slug="engineering-internship")`
_Interface labels:_ Filter by unit · Filter by city · Filter by work model · All units · All cities · All models · Open roles: {count} · View details · No roles in this selection · No open role matches these filters right now. Reset the filters or send an open application. · Reset filters · Send an open application · Close · About the role · Copy link · Link copied · APPLICATION · OPEN APPLICATION · Apply for {role} · Open application · Upload your CV as a PDF. HR and the relevant team review your application together, and we reply in writing whatever the outcome. · Leave your CV for a role that isn't listed. HR and the relevant team review it together, and we'll contact you when a matching role opens. · Back to role · Full name · Email · Role · Open application · Links · LinkedIn, GitHub or portfolio · Short note · Why this role? What piece of work did you own the most? · optional · {count}/{max} · CV · Drag your PDF here · or choose it from your device · Drop the file · PDF, up to 4 MB · Replace · Remove · PDF verified · Uploading · I agree that my CV and the details in this form are processed to evaluate my application. · PDPL privacy notice · Send application · Sending · We've received your application · Your CV is with HR and the relevant team. We'll reply in writing to {email} once they've reviewed it. · Close · Your application wasn't sent · Try again · Send by email · Your email app opens a message to {email}. You'll need to attach your CV yourself. · Application: {role} · Leave this field empty · {size} KB · {size} MB · Enter your full name. · Enter a valid email address. · Links can be up to {max} characters. · The note can be up to {max} characters. · Add your CV as a PDF. · This file is empty. Choose another PDF. · This file is {size}. The CV can be up to 4 MB. · This file isn't a PDF. Save your CV as a PDF and try again. · Add a single PDF file. · Tick the consent box to send your application. · Too many applications were sent in a short time. Try again in a few minutes. · The connection dropped. Check your internet connection and try again. · We can't send your application right now. Try again or send it by email.
## From application to offer
_HIRING PROCESS_
Five steps, and we tell you up front what we expect at each one.
> Timings are estimates and may vary with the role's scope and scheduling. Whatever the outcome, we reply in writing at the end of every step.
1. **Application** · _Written reply_
Upload your CV as a PDF through the application form and add links to code or design work if you have them. HR and the relevant team review your application together.
A short note: why this role, and which piece of work you owned the most.
HR and the role's team review your application together, and we reply in writing.
**Sample candidate journey**
- Form: PDF CV and GitHub link sent
- HR and the Hub team reviewed the application together
- Times proposed for an intro call
2. **Intro call** · _30 minutes_
A video call with someone from the team. We talk through the role, the team and how we work, and leave time for your questions.
Being open about your expectations and your preferred work model.
We explain the role's actual scope, the team and the next steps.
**Sample candidate journey**
- Video call invite accepted
- Role scope and work model discussed
- Candidate chose the take-home as the technical format
3. **Technical exercise** · _Take-home or 90-minute session_
We offer two options: a scoped take-home you do on your own time, or a live pairing session with someone from the team.
Choosing the format you prefer and explaining your decisions.
We keep the scope clear and state the expected time for the take-home up front.
**Sample candidate journey**
- Take-home scope and expected time shared in writing
- Candidate submitted the solution with a short decision note
- Two engineers reviewed the solution
4. **Team interview** · _60 minutes_
We go through your technical exercise with the team you'd join and talk through how real work moves forward.
Discussing the trade-offs and alternatives in your work.
We show you the team's day-to-day work and how review and release run.
**Sample candidate journey**
- Trade-offs in the take-home discussed
- Team walked through its review and release routine
- Team shared its feedback in writing
5. **Offer** · _Written offer_
Once we've decided, we send the offer in writing and agree on the role, work model and start date together.
Sharing your questions and your preferred start date.
We set out every part of the offer clearly and in writing.
**Sample candidate journey**
- Offer sent with role, work model and start date
- Candidate's questions answered
- Start date agreed together
- **Sample candidate journey:** Backend Engineer application
_Interface labels:_ What we ask of you · On our side
## For everyone on the team
_WORKING CONDITIONS_
Whatever the unit, city or work model.
- **Live products**
You work on Pals, L.I.T. and client projects that are live.
- **Equipment**
The company provides a computer, a monitor and the test devices your role needs.
- **Time to learn**
Reading and trying out a new tool count as working time.
- **Flexible hours**
The work model depends on the role; outside the team's shared hours, you set your own schedule.
- **Pairing**
You work on the same tasks as senior teammates and review each other's work.
- **Written scope**
The role's scope and how it is evaluated are shared in writing before you start.
_Representative interface data_
- **clientWork:** Client projects
- **workTime:** Working hours
- Project work
- Code review
- Reading and trying
- **coreHours:** Shared hours
**Role scope**
- Area of ownership
- Evaluation criteria
- Work model
- Start date
- Computer
- Monitor
- Test devices
## Don't see your role listed?
_OPEN APPLICATION_
Share your CV and what you'd like to work on. HR and the relevant team review it together, and we'll contact you when a matching role opens.
- [Send an open application](https://oxarus.com/en/careers?apply=open#roles) → `apply_role(slug="open")`
## Actions
- [View roles](https://oxarus.com/en/careers#roles) → `open_page(path="/careers", anchor="roles")`
- [Hiring process](https://oxarus.com/en/careers#process) → `open_page(path="/careers", anchor="process")`
- [Send an open application](https://oxarus.com/en/careers?apply=open#roles) → `apply_role(slug="open")`
- [Türkçe](https://oxarus.com/tr/careers) → `switch_locale(locale="tr", path="/careers")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "Contact: Talk to Oxarus about your project"
description: "One point of contact for Hub, Studio, Agent AI and Quant. Start with a detailed brief or a short message; the relevant team reads it and gets back to you."
url: https://oxarus.com/en/contact
key: contact
route: /contact
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/contact
en: https://oxarus.com/en/contact
documents:
json: https://oxarus.com/machine/en/contact.json
jsonld: https://oxarus.com/machine/en/contact.jsonld
txt: https://oxarus.com/machine/en/contact.txt
schema: oxarus.machine/2.0
---
# Contact: Talk to Oxarus about your project
> One point of contact for Hub, Studio, Agent AI and Quant. Start with a detailed brief or a short message; the relevant team reads it and gets back to you.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Contact](https://oxarus.com/en/contact)
## Notices
- Interface data marked as representative is illustrative; it is not a real client, result or measurement.
## Sections
- [Let's talk about your project](#hero)
- [Leave a quick note](#quick)
- [Reach us however suits you](#channels)
- [Ankara and Istanbul](#offices)
- [Before we start](#faq)
## Let's talk about your project
_CONTACT_
Tell us what you want to build. Your message goes to the people on the Hub, Studio, Agent AI or Quant team who would run the project.
- Read by the team that runs the project
- No sales pitch on the first call
- Scope and proposal in writing
- [Start a project](https://oxarus.com/en/contact#start) → `start_project_brief()`
- [Quick message](https://oxarus.com/en/contact#quick-message) → `open_page(path="/contact", anchor="quick-message")`
- **phone:** Phone
_Representative interface data_
**Inbox**
> Illustrative examples
- **reading:** Reading the subject
- **routed:** Routed to team
- **lanesLabel:** Teams
- _Hub_
- **from:** Retail brand
- **subject:** We want to rebuild our corporate website and product catalog
- _Studio_
- **from:** Health startup
- **subject:** iOS and Android versions of our appointment app
- _Agent AI_
- **from:** Logistics company
- **subject:** We want to stop keying in incoming invoices by hand
- _Quant_
- **from:** Portfolio team
- **subject:** A custom MT5 robot for our own strategy
## Leave a quick note
_QUICK MESSAGE_
A few sentences is enough. Pick a topic and tell us what you need; the relevant team replies by email.
**Topic**
Hub · Studio · Agent AI · Quant · General
- [Send message](mailto:info@oxarus.com) → `contact()`
**Detailed brief**
Pin down the unit, scope, stage and timing in five steps. The team comes to the first call prepared.
- [Start a project](https://oxarus.com/en/contact#start) → `start_project_brief()`
_Representative interface data_
**What the team receives**
- **label:** Preview
- **draft:** Draft
- **sent:** Sent
- **to:** To
- **from:** From
- **subject:** Subject
- **team:** {unit} team
- **name:** Your name
- **email:** your email
- **message:** Your message shows up here.
_Interface labels:_ Sending · Your message reached us · Thank you. The relevant team will read your message and reply by email. · Write a new message · We'll reply to {email}. · Message not sent · The form isn't responding right now. You can send what you wrote by email instead. · Send by email · Try again
## Reach us however suits you
_DIRECT CHANNELS_
Email, phone or a project brief. All three reach the relevant team.
1. **We read your message**
The team that would run the project reviews your request and asks if anything is missing.
2. **We hold an intro call**
In a short call, we clarify the goal, the constraints and where things stand today.
3. **We send a written scope**
We share the work, the delivery steps and the proposal in writing.
- **Email**
One address for every unit. Attach files, briefs and any existing documents.
- [Write an email](mailto:info@oxarus.com) → `contact()`
- **Phone**
Call with a quick question or to set up a meeting.
- **call:** Call
- **Project brief**
Choose the unit, scope and timing step by step; the brief reaches the team as a single message.
- [Start the brief](https://oxarus.com/en/contact#start) → `start_project_brief()`
- **Careers**
For open roles and general applications, use the careers page.
- [View open roles](https://oxarus.com/en/careers) → `open_page(path="/careers")`
_Interface labels:_ After your message · Copy address · Copied · Copy number · Copied · {count} open roles
## Ankara and Istanbul
_OFFICES_
Engineering in Ankara, operations and architecture in Istanbul. Projects are run by both offices together.
- **Ankara**
Engineering & R&D
Software development, automation and Quant research happen at this office.
- **coords:** 39.93° N · 32.86° E
Studio · Agent AI · Quant
**At this office**
- Web and mobile product development
- Agent AI workflows
- Quant research and data infrastructure
- **Istanbul**
Operations & Architecture
Project management, solution architecture and client operations are run from this office.
- **coords:** 41.01° N · 28.98° E
Hub · Studio · Agent AI · Quant
**At this office**
- Project planning and management
- Solution architecture
- Client operations
- **bridge:** Shared repo, shared process
_Interface labels:_ Units
## Before we start
_FAQ_
The questions we hear most before a first call.
**Question:** What should I bring to get started?
**Answer:** Whatever you have is enough: a short description, examples you like, design files or the URL of your current product. We fill in the gaps together on the intro call.
**Question:** Do you sign NDAs?
**Answer:** Yes. If you'd like an NDA before sharing details, we can use your own template or our standard one.
**Question:** How is pricing set?
**Answer:** We don't have fixed package prices. After the intro call, we define the scope and prepare a written proposal broken down by work item.
**Question:** Can you work alongside our existing team?
**Answer:** Yes. We can work with your own engineering or design team through a shared repo, a shared process and a clear split of responsibilities.
**Question:** What kind of Quant requests do you take on?
**Answer:** Custom MT5 robot development for your own strategy, the L.I.T. early-access list, and research and data infrastructure projects.
**Question:** Do you offer maintenance after delivery?
**Answer:** Yes. After delivery, we define a separate support scope for maintenance, updates and further development.
**Don't see your question?**
Send a short email or start the brief; the relevant team will answer.
- [Start a project](https://oxarus.com/en/contact#start) → `start_project_brief()`
## Actions
- [Start a project](https://oxarus.com/en/contact#start) → `start_project_brief()`
- [Quick message](https://oxarus.com/en/contact#quick-message) → `open_page(path="/contact", anchor="quick-message")`
- [Send message](mailto:info@oxarus.com) → `contact()`
- [View open roles](https://oxarus.com/en/careers) → `open_page(path="/careers")`
- [Türkçe](https://oxarus.com/tr/contact) → `switch_locale(locale="tr", path="/contact")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "Privacy Policy"
description: "Privacy policy of the Oxarus website: what information is collected, how it is used, who it is shared with and how it is protected."
url: https://oxarus.com/en/legal/privacy
key: legal-privacy
route: /legal/privacy
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/legal/privacy
en: https://oxarus.com/en/legal/privacy
documents:
json: https://oxarus.com/machine/en/legal/privacy.json
jsonld: https://oxarus.com/machine/en/legal/privacy.jsonld
txt: https://oxarus.com/machine/en/legal/privacy.txt
schema: oxarus.machine/2.0
---
# Privacy Policy
> Privacy policy of the Oxarus website: what information is collected, how it is used, who it is shared with and how it is protected.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Privacy Policy](https://oxarus.com/en/legal/privacy)
## Sections
- [Privacy Policy](#intro)
- [Scope](#scope)
- [Information we collect](#collect)
- [How we use information](#use)
- [Sharing information](#sharing)
- [Security](#security)
- [Cookies](#cookies)
- [Links to other sites](#links)
- [Children's privacy](#children)
- [Your rights](#rights)
- [Changes](#changes)
- [Contact](#contact)
## Privacy Policy
This page explains in plain language what information we collect when you use our website, what we use it for and how we protect it.
- **Last updated:** September 18, 2026
- **Published by:** OXARUS YAZILIM A.Ş.
## Scope
This policy applies to the oxarus.com website operated by OXARUS YAZILIM A.Ş. (“Oxarus”, “we”) and to the forms on the site.
The statutory notice on the processing of personal data is our PDPL Privacy Notice, prepared under the Turkish Personal Data Protection Law No. 6698 (PDPL). Please read this policy together with that notice.
Data we process on behalf of our clients in the systems we build for them is not covered by this policy. That data is governed by the relevant contract and by our clients' own privacy notices.
- [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
## Information we collect
### Information you give us
- **Project brief form:** Name, email, optional company name, the unit and scope you select, project stage, timing and budget range, and your message.
- **Quick message form:** Name, email, the topic you pick and your message.
- **L.I.T. early access form:** Name, email and the modules you are most interested in.
- **Job application form:** Name, email, the role you apply for, the links you share, your short note and your CV as a PDF.
- **Email and phone:** The contact details you share when you write to us or call us, and the content of that correspondence.
### Information created automatically
- When you visit the site, server logs record technical details such as your IP address, browser and device information, the time of access and the page requested.
- When you send a form, the page it was sent from and the site language are sent along with your message.
- To prevent abuse, form submissions are rate limited by IP address.
- Your language preference and your cookie choice are each kept in a cookie; a project brief draft is kept only in your open browser tab.
- If you allow analytics, Google Analytics records the pages you view, how you move through the site, your device and browser type and your approximate location through cookies.
> We do not use cookies or pixels for advertising or marketing. Google Tag Manager and Google Analytics load only if you allow them.
## How we use information
- To answer your request or message, prepare proposals and hold project discussions
- To send L.I.T. early access invitations
- To review job applications and contact applicants
- To keep the site secure, find errors and block unwanted submissions
- If you allow analytics, to measure how the site is used and improve it
- To meet our legal obligations and protect our rights
We do not add form details to marketing lists, and we do not send you promotional messages without your consent. Your messages and applications are reviewed by our team; we use no system that makes automated decisions about people.
## Sharing information
We do not sell your information or share it with anyone for advertising. We share it only in the cases below, and only as far as needed:
- With service providers in Türkiye and abroad that provide hosting, email and form notification services, as far as the service requires
- If you allow analytics, with Google Ireland Limited and Google LLC, which provide Google Analytics, as far as that service requires
- With legal, accounting and audit advisers, under a duty of confidentiality
- With courts and public authorities legally entitled to request information, under our legal obligations
Transfers abroad are made in line with the conditions of Article 9 of Law No. 6698. You can find the details in our PDPL Privacy Notice.
## Security
We take reasonable technical and organizational measures to protect your information against unauthorized access, loss and misuse:
- The connection between the site and your browser is encrypted.
- Form submissions are validated on the server, with rate limits and automated submission filters.
- CVs are accepted only as PDF files within a size limit; the file type and name are checked.
- Applications and messages are accessed only by the employees who need to review them.
- We choose our service providers with their security and confidentiality obligations in mind.
No transmission over the internet is completely free of risk. If we become aware of a security breach affecting your personal data, we notify the Personal Data Protection Board and, where required, you, as the law provides. Our PDPL Privacy Notice sets out the measures and the notification process in detail.
- [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
## Cookies
The site uses two strictly necessary cookies that remember your language and your cookie choice, and browser storage that keeps a project brief draft until you close the tab.
If you allow analytics, Google Analytics loads through Google Tag Manager to measure how the site is used, and its cookies are set. If you don't, neither is loaded. You can change your choice at any time through the Cookie settings link at the bottom of every page. Our Cookie Policy explains each cookie and how long it is kept.
- [Cookie Policy](https://oxarus.com/en/legal/cookies)
## Links to other sites
Our site links to our social media accounts, client projects and other websites. We do not control the privacy practices of those sites, so we recommend reading their own policies when you visit them.
## Children's privacy
Our site and forms are not designed for people under 18. If you are under 18, please do not send us information through our forms. If we learn that a child's information has been sent to us, we delete it.
## Your rights
Your rights, such as accessing your personal data, asking for it to be corrected or deleted and withdrawing your consent, and how to exercise them are explained in detail in our PDPL Privacy Notice.
To leave the early access list or ask us to delete a message or application, just write to info@oxarus.com.
- [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
## Changes
We update this policy when our practices on the site or the law change. The current version is always published on this page and takes effect on the date it is published; the last updated date appears at the top of the page.
## Contact
For questions about privacy, you can reach us using the details below.
- **Legal name:** OXARUS YAZILIM A.Ş.
- **Address:** Ümit Mah. 2540 Sk. No:17/A Çankaya / ANKARA
- **Email:** info@oxarus.com
- **Phone:** +90 312 980 00 94
## Actions
- [Türkçe](https://oxarus.com/tr/legal/privacy) → `switch_locale(locale="tr", path="/legal/privacy")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "PDPL Privacy Notice"
description: "How Oxarus processes personal data on its website and forms under Turkish Law No. 6698: purposes, legal grounds, transfers, retention and your rights."
url: https://oxarus.com/en/legal/kvkk
key: legal-kvkk
route: /legal/kvkk
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/legal/kvkk
en: https://oxarus.com/en/legal/kvkk
documents:
json: https://oxarus.com/machine/en/legal/kvkk.json
jsonld: https://oxarus.com/machine/en/legal/kvkk.jsonld
txt: https://oxarus.com/machine/en/legal/kvkk.txt
schema: oxarus.machine/2.0
---
# PDPL Privacy Notice
> How Oxarus processes personal data on its website and forms under Turkish Law No. 6698: purposes, legal grounds, transfers, retention and your rights.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
## Sections
- [PDPL Privacy Notice](#intro)
- [Data controller](#controller)
- [Personal data we process](#data)
- [Special categories](#sensitive)
- [Purposes of processing](#purposes)
- [Legal grounds](#grounds)
- [Consent and withdrawal](#consent)
- [Transfers and recipients](#transfers)
- [How we collect data](#collection)
- [Retention periods](#retention)
- [Data security](#security)
- [Breach notification](#breach)
- [Automated decisions](#automated)
- [Children's data](#children)
- [VERBİS registration](#verbis)
- [Your rights](#rights)
- [How to apply](#requests)
- [Changes](#changes)
## PDPL Privacy Notice
Under Article 10 of the Turkish Personal Data Protection Law No. 6698 (PDPL, known in Turkish as KVKK), we inform the people who visit our website, fill in our forms or contact us about how their personal data is processed.
- **Last updated:** September 18, 2026
- **Published by:** OXARUS YAZILIM A.Ş.
## Data controller
Under Personal Data Protection Law No. 6698 (the “Law”), your personal data is processed by OXARUS YAZILIM A.Ş. (“Oxarus”, “we”) as data controller.
- **Legal name:** OXARUS YAZILIM A.Ş.
- **Head office:** Ümit Mah. 2540 Sk. No:17/A Çankaya / ANKARA
- **MERSIS number:** 0734250410500001
- **Phone:** +90 312 980 00 94
- **Email:** info@oxarus.com
This notice covers personal data processed through the oxarus.com website and its project brief, quick message, L.I.T. early access and job application forms. All of our company details are on the Company Information page.
- [Company Information](https://oxarus.com/en/legal/company)
## Personal data we process
Which of your data is processed depends on how you use the site:
- **Identity:** First and last name.
- **Contact:** Email address; your phone number when you call us or share it in correspondence.
- **Request and project:** Company name, the unit and scope you select, project stage, timing and budget range, your message, and the page and language the form was sent from.
- **Early access:** The modules you are most interested in, for the L.I.T. early access list.
- **Job application:** The role you apply for, the links you share (such as LinkedIn, GitHub or a portfolio), your short note and the education, work experience and skills in your CV.
- **Transaction security:** Server logs such as IP address, browser and device information, time of access and the page requested; records of the rate limits applied to form submissions.
- **Preference:** Your language preference and your cookie choice.
- **Usage (analytics):** If you allow analytics, the data collected with the Google Analytics cookies: pages viewed, navigation and interactions on the site, device and browser information, approximate location (country and city level) and cookie IDs.
### Required and optional fields
- The project brief and quick message forms require your name, email, message and the consent box; the company name and the other fields are optional.
- A job application requires your name, email, the role, a PDF CV and the consent box; links and the short note are optional.
- The L.I.T. early access form requires your name, email and the consent box; the modules you pick are optional.
Leaving optional fields empty does not stop us from reviewing your request.
## Special categories
We do not ask for special categories of personal data in our forms — health information, religious beliefs, membership of an association, foundation or trade union, criminal convictions and the like — and we do not aim to process them.
In a job application you upload your CV yourself and we do not decide what is in it. If it contains data of this kind, we do not use it to assess your application.
Special category data sent to us without being asked for is left out of the assessment, stays accessible only to the people reviewing the application, and is deleted together with your application file at the end of the retention period.
> Please do not include special categories of personal data in your CV or messages; we do not need them to review your application.
## Purposes of processing
We process your personal data for the following purposes:
- To review project requests and messages, get back to you and prepare proposals
- To hold pre-contract discussions and establish a service relationship
- To manage the L.I.T. early access list and send invitations
- To review job applications, contact applicants and run the hiring process
- To keep the website and forms secure and prevent abuse and unwanted submissions
- To remember your language and cookie choices and provide the functions the site needs to work
- If you allow analytics, to measure how the site is used and improve it
- To meet our legal obligations, respond to requests from competent authorities and protect our rights in possible disputes
## Legal grounds
We process your personal data on the following legal grounds listed in Article 5 of the Law:
- **Entering into or performing a contract (Art. 5/2-c):** Reviewing your project request, preparing proposals and pre-contract discussions; reviewing your job application.
- **Legal obligation (Art. 5/2-ç):** Record-keeping obligations and obligations to provide information to competent authorities under the law.
- **Establishing, exercising or protecting a right (Art. 5/2-e):** Keeping the records needed in possible disputes.
- **Legitimate interest (Art. 5/2-f):** Answering general messages, managing the early access list, remembering your language and cookie choices, keeping the site secure and preventing abuse, provided this does not harm your fundamental rights and freedoms.
- **Explicit consent (Art. 5/1):** The cases listed in the next section: the consent boxes on our forms and the analytics cookies.
## Consent and withdrawal
Most of your personal data is processed on the other grounds above rather than on consent. We ask for explicit consent in these cases:
- The consent you give by ticking the box on the project brief and quick message forms, so we can respond to your request, and on the L.I.T. early access form, so we can manage the list and contact you about your invitation
- The consent you give by ticking the box on the job application form, so that your CV and application details can be reviewed
- The consent you give by allowing analytics in the cookie notice or in Cookie settings, for the Google Analytics cookies and for the transfer abroad of the data they collect
- The separate consent you give for us to keep your application for future roles after the retention period ends
- Any consent we collect in advance under Turkish Law No. 6563 if we ever start sending marketing messages
We do not send marketing messages today. If you join the L.I.T. early access list, we only write to you about your invitation.
You can withdraw your consent at any time by writing to info@oxarus.com. When you do, we stop the processing concerned and delete your data unless another legal ground requires us to keep it. Withdrawal does not affect the lawfulness of processing carried out before it.
You can also withdraw your analytics consent through the Cookie settings link at the bottom of every page. When you do, the Google Analytics cookies are deleted from your browser, and Google Tag Manager and Google Analytics are not loaded until you allow them again.
## Transfers and recipients
We do not sell your personal data or share it with third parties for advertising. As far as needed for the purposes above, and in line with Articles 8 and 9 of the Law, we may transfer it to the following groups of recipients:
- **Service providers:** Providers in Türkiye and abroad that we use for website hosting and infrastructure (such as DigitalOcean), domain and email delivery services, form notifications and IT support. They process your data only as far as the service requires and on our instructions.
- **Analytics provider:** If you allow analytics, Google Ireland Limited and Google LLC, which provide Google Tag Manager and Google Analytics, only as far as these services require.
- **Advisers:** Legal, accounting and audit advisers, under a duty of confidentiality and only as far as needed.
- **Competent authorities:** Courts, enforcement offices and other public authorities legally entitled to request information, under our legal obligations.
### Transfers abroad
Some of the providers we use for hosting, infrastructure and email delivery keep their servers outside Türkiye. In that case your personal data is transferred in line with the conditions of Article 9 of the Law:
- An adequacy decision of the Personal Data Protection Board exists for the country, sector or international organization receiving the data
- Where there is no adequacy decision, one of the appropriate safeguards listed in the Law is in place, such as standard contractual clauses notified to the Board
- Where neither applies, the transfer is only incidental and relies on one of the exceptions listed in the Law
If you allow analytics, the data collected with the Google Analytics cookies is transferred to Google's servers outside Türkiye, including in the United States. This transfer relies on your explicit consent under Article 9 of the Law. The level of personal data protection in the countries the data goes to may not be the same as in Türkiye. If you don't allow analytics, this transfer does not take place.
Apart from the transfers these services and the analytics you allow require, we do not send your personal data abroad.
## How we collect data
We collect your personal data partly by automated means, through the website forms and server logs, and by non-automated means, through email, phone and written requests:
- Project brief and quick message forms
- L.I.T. early access form
- Job application form on the careers page
- Requests sent through the site's interfaces by AI assistants acting for you and with your approval
- Email, phone and written correspondence
- Server logs and the language preference and consent cookies created while you visit the site
- The Google Analytics cookies, when you allow analytics
This data is collected for the purposes in the purposes section and on the legal grounds explained in the legal grounds section. Server logs are created automatically as you use the site; our Cookie Policy explains the cookies and the browser storage in detail.
- [Cookie Policy](https://oxarus.com/en/legal/cookies)
## Retention periods
We keep your personal data for as long as the purpose of processing requires and for the periods set by the applicable law. Our general retention periods are:
| Data | Retention period |
| --- | --- |
| Project requests and messages | Until the request is closed and for as long as the business relationship lasts; after that, for the applicable statutory limitation periods |
| L.I.T. early access list | Until your invitation is sent or you ask to leave the list |
| Job applications | Up to 1 year after the application is closed; we ask for your explicit consent to keep it longer |
| Server and security logs | For as long as the security purpose requires and for the periods set by the applicable law |
| Language preference cookie | Up to 1 year in your browser |
| Consent cookie | 12 months in your browser |
| Google Analytics cookies | Up to 2 years in your browser; deleted when you withdraw your consent |
When the period ends or the reason for processing no longer exists, we delete, destroy or anonymize your personal data on our own initiative or at your request.
## Data security
The main organizational and technical measures we take to protect your personal data against unauthorized access, loss and misuse:
- **Limited access:** Messages, briefs and applications are accessed only by the people who need to review them; access rights are reviewed as roles change and everyone works under a duty of confidentiality.
- **Encrypted transmission:** The connection between the site and your browser, and the form submissions themselves, are encrypted in transit.
- **Data minimization:** Our forms ask only for what we need to review your request; we do not collect data we have no use for and do not keep data past its period.
- **Protection against abuse:** Form submissions are validated on the server, with rate limits and automated submission filters. CVs are accepted only as PDF files within a size limit, and the file type and name are checked.
- **Logging:** Server logs are kept to detect and investigate security incidents, for as long as that purpose requires.
- **Choice of providers:** We choose our service providers with their privacy and security obligations in mind and put contracts in place where needed.
No transmission over the internet is completely free of risk; we review our measures as the law and the technology change.
## Breach notification
If we find that your personal data has been obtained unlawfully by others, we notify the Personal Data Protection Board within 72 hours of becoming aware of it, as Article 12 of the Law requires.
We also inform the people affected as soon as reasonably possible, explaining when and how the breach happened, which data it covers, its likely consequences, the measures we have taken and what you can do.
If you notice a security problem, you can report it to us at info@oxarus.com.
## Automated decisions
We do not carry out automated decision-making or profiling that produces legal effects for you. Your messages, briefs and job applications are read and assessed by our team.
The machine view, document endpoints and agent interfaces on the site only serve the site's public content and, with your approval, pass your request on to us. They do not assess or score people.
The automatic rate limit that prevents abuse is a technical security measure and produces no decisions about people.
## Children's data
Our site and forms are not aimed at people under 18 and we do not knowingly collect personal data from children. If you are under 18, please do not send us information through our forms.
If we learn that a child's personal data has been sent to us, we delete it unless a legal ground requires us to keep it.
## VERBİS registration
Registration with VERBİS (the data controllers' registry) is mandatory for controllers above the thresholds set by the Personal Data Protection Board. Controllers with fewer than 50 employees a year and an annual balance sheet total below TRY 25 million, whose main activity is not the processing of special categories of personal data, are exempt from registration under Board decisions 2018/32 and 2019/265.
Oxarus meets these criteria and is therefore not currently registered with VERBİS.
If we exceed the thresholds or our activities change, we will register within the period the law provides and update this notice.
## Your rights
Under Article 11 of the Law, you can contact us to exercise the following rights:
1. To learn whether your personal data is processed
2. To request information about the processing if it is
3. To learn the purpose of processing and whether the data is used in line with that purpose
4. To know the third parties in Türkiye or abroad to whom your personal data is transferred
5. To ask for your personal data to be corrected if it is incomplete or inaccurate
6. To ask for your personal data to be deleted or destroyed under the conditions of Article 7 of the Law
7. To ask for corrections, deletions or destructions to be notified to the third parties to whom your personal data was transferred
8. To object to a result against you arising from the analysis of your data exclusively by automated systems
9. To claim compensation if you suffer damage because your personal data is processed unlawfully
Where processing is based on consent you can also withdraw it; the “Consent and withdrawal” section explains how.
## How to apply
You can send requests about your rights in one of the following ways, in line with the Communiqué on the Procedures and Principles of Application to the Data Controller:
- By a signed written application delivered by hand to Ümit Mah. 2540 Sk. No:17/A Çankaya / ANKARA, sent by registered post with proof of delivery, or served through a notary
- By email to info@oxarus.com, signed with a secure electronic signature or mobile signature
- By email to info@oxarus.com from an email address you have previously given us and that is registered in our systems
### What your application must include
- Your first and last name and, for written applications, your signature
- For citizens of the Republic of Türkiye, the Turkish ID number; for foreign nationals, nationality and passport number or ID number if any
- Your residential or business address for notifications
- Your email address for notifications, phone and fax number, if any
- The subject of your request
### Identity checks and fees
Before we answer, we need to be sure the request really comes from you, so we may ask for extra information to verify your identity. If you apply on someone else's behalf, we ask for a document showing your authority. We cannot send an answer containing personal data when we cannot verify the applicant's identity.
We conclude your request free of charge as soon as possible depending on its nature, and within 30 days at the latest. If the process involves an additional cost, we may ask for the fee in the tariff set by the Personal Data Protection Board under Article 7 of the Communiqué.
If your request is rejected, you find the answer insufficient or we do not answer in time, you can file a complaint with the Personal Data Protection Board within 30 days of learning of the answer and in any case within 60 days of your application.
## Changes
We may update this notice to reflect changes in our processing activities or in the law. The current version is always published on this page; the last updated date appears at the top of the page.
- [Privacy Policy](https://oxarus.com/en/legal/privacy)
- [Cookie Policy](https://oxarus.com/en/legal/cookies)
## Actions
- [Türkçe](https://oxarus.com/tr/legal/kvkk) → `switch_locale(locale="tr", path="/legal/kvkk")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "Terms of Use"
description: "Terms of use of the Oxarus website: rules of use, intellectual property, representative content, market content, liability, governing law and competent courts."
url: https://oxarus.com/en/legal/terms
key: legal-terms
route: /legal/terms
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/legal/terms
en: https://oxarus.com/en/legal/terms
documents:
json: https://oxarus.com/machine/en/legal/terms.json
jsonld: https://oxarus.com/machine/en/legal/terms.jsonld
txt: https://oxarus.com/machine/en/legal/terms.txt
schema: oxarus.machine/2.0
---
# Terms of Use
> Terms of use of the Oxarus website: rules of use, intellectual property, representative content, market content, liability, governing law and competent courts.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Terms of Use](https://oxarus.com/en/legal/terms)
## Sections
- [Terms of Use](#intro)
- [Parties and scope](#parties)
- [Rules of use](#use)
- [Intellectual property](#content)
- [Representative content](#representative)
- [Not investment advice](#quant)
- [Accuracy of information](#accuracy)
- [External links](#external)
- [Limitation of liability](#liability)
- [Forms and applications](#forms)
- [Governing law](#law)
- [Contact](#contact)
## Terms of Use
These terms set out the rules that apply when you use the Oxarus website. By using the site, you accept them.
- **Last updated:** September 17, 2026
- **Published by:** OXARUS YAZILIM A.Ş.
## Parties and scope
The oxarus.com website (the “site”) is operated by OXARUS YAZILIM A.Ş. (“Oxarus”, “we”). These terms apply to everyone who visits and uses the site.
Project, service and employment contracts made with Oxarus are separate from these terms. If a contract and these terms differ, the contract prevails.
## Rules of use
You agree to use the site lawfully and in line with these terms. In particular, you must not:
- Attempt to disrupt the site, overload it or get around its security measures
- Send fake, misleading, bulk or unsolicited content through the forms or programmatic interfaces
- Submit other people's personal data or information that belongs to someone else without authorization
- Upload files containing malicious software
- Copy the site's content without permission or use it in a way that suggests you are affiliated with Oxarus
Machine-readable versions of the site (Markdown documents, llms.txt and agent interfaces) are published for search engines and AI assistants. Software that sends requests through these interfaces must do so only with the approval of the person concerned and within the rate limits.
## Intellectual property
The text, designs, logos, images, interface examples and software code on the site belong to Oxarus or its licensors and are protected by intellectual property law. The names and logos of Oxarus, Oxarus Hub, Oxarus Studio, Oxarus Quant, Oxarus Agent AI and L.I.T. may not be used without written permission.
Client names, logos and project images on the showcase page belong to the clients concerned and are shown only to present our work.
You may quote short passages from the site as long as you credit the source and do not change their meaning. Any other use requires our written permission.
## Representative content
We use interface examples, demo screens, sample reports and interactive animations to explain our services. Screens marked “Representative”, and the brand names, people's names, figures and results in them, are illustrative; they do not depict a real client, person or achieved result.
Scope, timelines and pricing are set for each project in a separate proposal and contract. Descriptions on the site are not an offer.
## Not investment advice
The research, L.I.T. screens, robot examples and other market content on the Oxarus Quant pages are for information and for presenting our services only. They are not investment advisory services, investment advice or a recommendation to buy or sell any financial instrument.
Investment advisory services are provided under an investment advisory agreement signed with authorized institutions. The information on the site may not suit your financial situation or preferences, and you should not make investment decisions based on it alone.
Trading leveraged products and other markets carries high risk, including the risk of losing the entire amount you invest. In our custom robot development service, the client defines the trading rules; Oxarus turns those rules into code and makes no commitment about how the robot performs in the market.
Oxarus trades in the markets with its own capital. This activity is not a service offered to third parties, and the site does not share information about its outcomes.
## Accuracy of information
We take care to keep the information on the site accurate and up to date, but we do not promise that the content is complete, error-free or always current. We may change the site's content, the services offered and these terms without prior notice.
We do not promise uninterrupted access to the site. It may be temporarily unavailable because of maintenance, updates or technical problems.
## External links
The site may link to websites and social media accounts that belong to third parties. We have no control over their content, security or privacy practices and are not responsible for them.
## Limitation of liability
The site and its content are provided “as is”. To the extent permitted by applicable law, Oxarus is not liable for direct or indirect damage arising from the use of or inability to use the site, from decisions made based on information on the site, or from third-party websites.
This limitation does not apply to damage caused by intent or gross negligence, or to liability that cannot be limited by law.
## Forms and applications
You are responsible for the accuracy of the information you send through the forms and for having the right to share any information that belongs to someone else.
Sending a form does not create a contract between you and Oxarus. Project and employment relationships are established by separate written contracts.
How the personal data you send is processed is explained in our PDPL Privacy Notice and Privacy Policy.
- [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
- [Privacy Policy](https://oxarus.com/en/legal/privacy)
## Governing law
These terms are governed by the laws of the Republic of Türkiye. The courts and enforcement offices of Ankara have jurisdiction over any dispute arising from these terms.
Users acting as consumers keep their right to apply to consumer arbitration committees and consumer courts under Consumer Protection Law No. 6502.
## Contact
For questions about these terms, you can reach us here.
- **Legal name:** OXARUS YAZILIM A.Ş.
- **Address:** Ümit Mah. 2540 Sk. No:17/A Çankaya / ANKARA
- **Email:** info@oxarus.com
- **Phone:** +90 312 980 00 94
## Actions
- [Türkçe](https://oxarus.com/tr/legal/terms) → `switch_locale(locale="tr", path="/legal/terms")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "Cookie Policy"
description: "The necessary cookies on the Oxarus website, and analytics that load only with your consent: what they do, how long they last and how to change your choice."
url: https://oxarus.com/en/legal/cookies
key: legal-cookies
route: /legal/cookies
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/legal/cookies
en: https://oxarus.com/en/legal/cookies
documents:
json: https://oxarus.com/machine/en/legal/cookies.json
jsonld: https://oxarus.com/machine/en/legal/cookies.jsonld
txt: https://oxarus.com/machine/en/legal/cookies.txt
schema: oxarus.machine/2.0
---
# Cookie Policy
> The necessary cookies on the Oxarus website, and analytics that load only with your consent: what they do, how long they last and how to change your choice.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Cookie Policy](https://oxarus.com/en/legal/cookies)
## Sections
- [Cookie Policy](#intro)
- [What cookies are](#what)
- [In short](#summary)
- [Cookies we use](#list)
- [Types of cookies](#types)
- [Legal ground](#grounds)
- [Managing cookies](#manage)
- [Changes](#changes)
## Cookie Policy
This page explains which cookies and browser storage our website uses, what they do and how you can manage them.
- **Last updated:** September 18, 2026
- **Published by:** OXARUS YAZILIM A.Ş.
## What cookies are
Cookies are small text files that a website you visit saves in your browser. Browser session storage (sessionStorage) and local storage (localStorage) also let websites keep information on your device.
In this policy we call all of them “cookies and similar technologies”. The policy applies to the website oxarus.com, which OXARUS YAZILIM A.Ş. operates.
## In short
- The site uses two cookies it needs to work, plus browser storage for a task you start yourself.
- Google Analytics cookies load through Google Tag Manager, and only if you allow analytics in the cookie notice or in Cookie settings.
- If you don't, neither Google Tag Manager nor Google Analytics is loaded, and no data is sent to Google for this purpose.
- No cookies are used for advertising or marketing, and the site has no pixels or embedded social media plugins.
- You can change your choice at any time through the Cookie settings link at the bottom of every page.
## Cookies we use
| Name | Type | Purpose | Duration |
| --- | --- | --- | --- |
| NEXT\_LOCALE | First-party cookie, strictly necessary | Remembers the language you chose (Turkish or English), so pages open in that language when you come back. | 1 year |
| oxarus\_consent | First-party cookie, strictly necessary | Remembers your choice in the cookie notice, that is whether you allow analytics, and when you made it, so the notice doesn't appear again on every page. | 12 months |
| oxarus:project-start:v1 | Session storage (sessionStorage), functional | Keeps what you type into the project brief form as a draft, so you can pick up where you left off after reloading the page. The draft is not sent to us. | Until the tab is closed; deleted immediately when the form is sent or you discard the draft |
| \_ga | First-party cookie, analytics (Google Analytics) | Holds a random ID to recognize your browser on later visits, so visits and page views can be measured. | Up to 2 years |
| \_ga\_C6NETFQR87 | First-party cookie, analytics (Google Analytics) | Keeps the session state, so visits can be measured as sessions. | Up to 2 years |
The language preference cookie holds only the value “tr” or “en” and contains no personal information. It is created when you open the site in a language other than your browser's language setting, or when you switch languages.
The consent cookie holds only your choice, the date you made it and a format version, and contains no personal information. It is created when you make a choice in the cookie notice or in Cookie settings.
The project brief draft is created only when you use the form, and it stays on your device. When you send the form, your details reach us in the message you send, not through the draft.
The Google Analytics cookies are created through Google Tag Manager, and only when you allow analytics. They are provided by Google Ireland Limited and Google LLC, and the usage data collected with them is processed on Google's servers outside Türkiye. When you withdraw your consent, these cookies are deleted from your browser.
## Types of cookies
- **Strictly necessary cookies:** Needed for the site's core functions. If you block them the site keeps working, but some preferences are not remembered. The language preference and consent cookies are of this type.
- **Functional storage:** Makes a task you started easier and is created only during that task. The project brief draft is of this type.
- **Analytics and performance cookies:** Help us measure how the site is used. The Google Analytics cookies are of this type and are used only with your explicit consent.
- **Advertising and marketing cookies:** Not used. Advertising permissions stay off even when you allow analytics.
## Legal ground
Because the language preference and consent cookies are strictly necessary for the site to work and to respect your choice, they rely on our legitimate interest under Article 5(2)(f) of Law No. 6698 and do not require explicit consent.
The Google Analytics cookies and the data collected with them rely on your explicit consent under Article 5(1) of the Law. The transfer of this data abroad also relies on your explicit consent; our PDPL Privacy Notice has the details.
The project brief draft is kept only in your browser and is not sent to us unless you send the form. How the details you send through the form are processed is explained in our PDPL Privacy Notice.
- [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
## Managing cookies
You can change your analytics choice at any time through the Cookie settings link at the bottom of every page. When you withdraw your consent, the Google Analytics cookies are deleted, Google Tag Manager is not loaded again until you allow it, and the page reloads once so the tag stops completely. Your choice is kept for 12 months; after that, the notice asks again.
You can also view, delete or block cookies and site data in your browser settings:
- In Chrome, Edge, Firefox, Safari and other browsers, these settings are in the privacy or site data section.
- On mobile devices, the same settings are in the browser's or the device's privacy settings.
- You can delete the project brief draft by choosing to discard it when you close the form, or by closing the tab.
If you block the language preference cookie, the site keeps working; only your language choice is not remembered on later visits. If you delete the consent cookie, the notice appears again and no analytics cookies are used until you choose.
## Changes
If the site starts using a new cookie or similar technology, we will update this policy. If we add a new cookie that needs consent, we will ask for your explicit consent again before using it.
For questions about cookies, write to info@oxarus.com.
## Actions
- [Türkçe](https://oxarus.com/tr/legal/cookies) → `switch_locale(locale="tr", path="/legal/cookies")`
## Related pages
- [Oxarus home](https://oxarus.com/en)
---
title: "Company Information"
description: "Legal name, head office address, MERSIS number and contact details of OXARUS YAZILIM A.Ş."
url: https://oxarus.com/en/legal/company
key: legal-company
route: /legal/company
unit: company
locale: en
status: live
alternates:
tr: https://oxarus.com/tr/legal/company
en: https://oxarus.com/en/legal/company
documents:
json: https://oxarus.com/machine/en/legal/company.json
jsonld: https://oxarus.com/machine/en/legal/company.jsonld
txt: https://oxarus.com/machine/en/legal/company.txt
schema: oxarus.machine/2.0
---
# Company Information
> Legal name, head office address, MERSIS number and contact details of OXARUS YAZILIM A.Ş.
Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Company Information](https://oxarus.com/en/legal/company)
## Sections
- [Company Information](#intro)
- [Registered details](#identity)
- [Contact details](#contact)
- [Business areas](#brands)
- [Correspondence and requests](#correspondence)
## Company Information
We publish our company details on this page under Article 1524 of Turkish Commercial Code No. 6102.
- **Last updated:** September 17, 2026
- **Published by:** OXARUS YAZILIM A.Ş.
## Registered details
- **Legal name:** OXARUS YAZILIM A.Ş.
- **Head office:** Ümit Mah. 2540 Sk. No:17/A Çankaya / ANKARA
- **MERSIS number:** 0734250410500001
## Contact details
- **Phone:** +90 312 980 00 94
- **Email:** info@oxarus.com
- **Website:** oxarus.com
Use email and phone for project requests and general questions, and our head office address for official correspondence.
## Business areas
Oxarus Hub, Oxarus Studio, Oxarus Quant and Oxarus Agent AI are the names of business areas run within OXARUS YAZILIM A.Ş., which provides the services offered under these names.
- **Oxarus Hub:** Corporate websites, visibility in AI search, e-commerce and custom business systems.
- **Oxarus Studio:** Web and mobile products, interface design and our own product, Pals.
- **Oxarus Quant:** Custom MetaTrader 5 robots, L.I.T. and market research.
- **Oxarus Agent AI:** AI agents that run business workflows with approval steps.
## Correspondence and requests
You can send official correspondence and legal notices to Ümit Mah. 2540 Sk. No:17/A Çankaya / ANKARA.
You can send requests about your personal data using the method described in our PDPL Privacy Notice.
- [PDPL Privacy Notice](https://oxarus.com/en/legal/kvkk)
## Actions
- [Türkçe](https://oxarus.com/tr/legal/company) → `switch_locale(locale="tr", path="/legal/company")`
## Related pages
- [Oxarus home](https://oxarus.com/en)