Questions? We have answers.

Qartivus is a software engineering firm. We build custom platforms, APIs, SaaS products, and backend systems for founders, CTOs, and businesses that need software they can trust in production for years, not something that holds up long enough to demo. We work with clients across Europe, the Gulf, and North Africa, from early-stage startups to established businesses going through digital transformation.

We are based in Tunisia. We serve clients remotely across Europe and the GCC region with no loss of communication quality, all project work is documented in English, French, or Hungarian, async-first, and structured around your timezone.

We operate as a senior-led engineering network. Every project is led directly by a senior engineer from architecture through to delivery, with the right specialists brought in based on what each project specifically requires. You always have a single point of accountability, not a rotating cast of unfamiliar faces.

Yes, always. We sign an NDA before any technical discussion begins. Most of our work is confidential by nature, we treat your codebase, architecture, and business logic as sensitive from day one.

Code Rescue is our service for teams who inherited or built a codebase they can no longer trust, AI-generated code, rushed development, or a previous vendor who disappeared. We offer three tiers: a Technical Audit that documents exactly what you have and what it's costing you; a Rescue Sprint that stabilises and patches the most critical issues; and a Full Rebuild for when the debt is too deep to recover. See the Code Rescue page for details.

Both. Greenfield builds are our preference, we love designing systems with no constraints. But a significant part of our work is rescuing and extending existing platforms. We're comfortable inheriting any codebase as long as we can do a proper audit first.

We build Android and iOS applications as well as mobile-first web applications. Whether native or web-based, we choose the approach that best fits your product's requirements and long-term maintainability.

Yes. We work with a trusted network of designers depending on the project's needs, UI/UX, brand identity, or both. If you already have a designer or brand guidelines, we implement them precisely. Design is never an afterthought in our process.

You own everything, code, documentation, infrastructure. We offer ongoing monthly retainers for teams who want continued engineering support, but there is no lock-in. You can take the codebase and run it independently from day one.

With a written brief. Before any code is written, we align on the problem, the scope, the milestones, and the definition of done. You receive a clear proposal before we start. No surprises, no scope creep that wasn't agreed on paper.

All communication goes through our CEO, who is also the technical founder. You are never handed off to a project manager or account executive, the person you speak to understands your codebase, your architecture, and your business context directly. Async-first by default, with structured updates and documented decisions at every milestone.

You do. Always. From the first line written to the final deployment, the intellectual property is yours. We do not retain any rights to your codebase, your data, or your architecture.

Yes. The repository is shared with you from day one. You can review every commit, every decision, every line, that transparency is part of what we mean by software you can own.

We treat GDPR as an architectural constraint, not a legal checkbox. Consent flows, data export endpoints, account deletion, and marketing consent separation are modelled into the application layer from the start, not patched in before launch. For clients in the EU and GCC, we document all data flows and third-party dependencies as part of standard delivery.

Yes. We work well alongside in-house engineers, product managers, and designers. We adapt to your existing tools and workflows rather than imposing ours. The only non-negotiable is a written brief before development starts, regardless of team structure.

Yes, and often. We are comfortable translating business requirements into technical architecture without requiring the client to know the difference between a REST API and a database schema. That translation work is part of what you're paying for.

Every project includes automated tests across core domains, code review at every pull request, and documented architecture decisions. We do not ship code that hasn't been read and understood by a senior engineer. That is not a process we follow, it is how we work.

Yes, always. Automated tests are not optional or an add-on, they are part of every delivery. We write tests that cover authentication flows, core business logic, edge cases, and regression risks. You receive test coverage reports as part of standard handoff.

Security is designed in, not bolted on. Rate limiting, CORS configuration, credential management, input validation, and access control are part of the architecture from day one. We follow OWASP guidelines and treat your threat model as a first-class requirement, not something to address after launch.

No. Hostnames, internal diagrams, security configurations, and implementation details stay in private client handover documentation. What we publish publicly is reviewed and approved by the client before it goes live.

Yes. We do this regularly through Code Rescue. The first step is always a Technical Audit, we need to understand what exists before we can responsibly extend or repair it. We will tell you honestly what we find, including if the codebase is beyond rescue and a rebuild is the only sensible path.

We understand why that question gets asked. The short answer: the person you speak to is the person accountable for your system. Every architectural decision is documented and yours to review. And we only take on projects we can genuinely deliver, if something is outside our scope, we say so before we start.

In rare cases, yes. If we see genuine potential in a project, a strong problem, a credible founder, and a market worth building for, we are open to a conversation about equity as part of the arrangement. This is not our default model, but we do not rule it out on principle.

Yes. We work in English and French natively, and we manage projects and communication in Hungarian. Our site is available in all three languages for exactly this reason.