Frequently asked questions

Use the quote wizard. It takes about three minutes; we review every request personally and reply with questions or a tailored proposal, usually within 1–2 business days.

Yes. We work remotely with clients across Europe, in English, Romanian, Hungarian and German.

After full payment, the deliverables created for your project belong to you, as described in the proposal. Third-party components keep their own licences, which we list.

Yes — from occasional updates to monthly support plans with monitoring, backups, security updates and small improvements.

Usually in milestones defined in the proposal — for example an advance at kickoff and the rest tied to delivered milestones. Small projects may use a simpler schedule.

Website development usually means a presentation or marketing site. Web development is the broader discipline that also covers web applications, portals, APIs and online stores.

No — nobody can honestly guarantee rankings. We build a strong technical and content foundation and set up the tools to measure progress; rankings then depend on competition and on the content you publish over time.

Yes. Every project includes an admin panel or CMS appropriate to its size, plus a short handover session.

A focused presentation website typically takes 3–6 weeks, depending mostly on how quickly content and feedback are ready. Larger multilingual sites take longer; you get a clear timeline in the proposal.

We help structure the content and can edit or write it with you. The best results come from combining your expertise about your business with our knowledge of how people read on the web.

Yes. We map old URLs to new ones with permanent redirects, keep valuable content and monitor Search Console after the switch.

You do — domain, content, design and code. We document the setup so any developer can continue the work.

A minimum viable product is the smallest version of your application that solves the core problem for real users. It reduces risk and cost, and lets real usage guide what to build next.

Yes. We choose proven technology, design the database carefully and keep the architecture simple enough to scale step by step instead of over-engineering on day one.

Through secure authentication, encryption in transit, role-based permissions, input validation, backups and audit logs — and by storing only the personal data the application truly needs.

We break the scope into features, estimate each one, add time for testing and project management, and state assumptions and exclusions explicitly. For uncertain projects we recommend a short paid discovery phase first.

Yes. The code lives in a repository you own or have full access to, along with documentation for setup and deployment.

Often, yes. We start with a code and infrastructure audit, then propose a plan: stabilise, improve or, in rare cases, rebuild parts.

The initial investment is usually higher, but there are no per-user licence fees and the software matches your process exactly. We help you compare both options honestly — sometimes an existing tool plus a small integration is the better choice.

Usually yes, through their official APIs or export formats. We check the available integration options during discovery.

Your data stays yours. We can host in the EU, document where data is stored and provide exports at any time.

Not native iOS apps at the moment — we focus on Android, where we can test thoroughly on real devices. If you also need to reach iPhone users, a progressive web app runs in the phone's browser and can be added to the home screen, from the same codebase.

Yes. We prepare the store listing and guide you through review. The developer account should be in your company's name, so you own the app listing.

Yes, if the use case allows it. Data can be stored on the device and synchronised when the connection returns — we design conflict handling so nothing gets lost.

It varies. New developer accounts and first submissions can take several days; updates are usually faster. Google may also require closed testing with real testers before production access for new personal accounts. We plan this time into the schedule.

We choose a minimum version that covers the vast majority of your target users while keeping development efficient, and always target the API level Google Play currently requires.

We can build a companion app that uses your existing backend, adding what the web can't do as well — notifications, offline access, device features. A plain "website in a wrapper" usually offers little value and may be rejected by Google Play.

If your needs are standard, a platform is usually faster and cheaper. Custom makes sense for unusual pricing, B2B workflows, configurators, very large catalogues or deep integrations. We recommend whichever is genuinely better for you.

Cards, Apple Pay and Google Pay through established payment processors, bank transfer and — if you want — cash on delivery. Availability depends on your processor and country.

Yes — products, customers and order history where the source platform allows export, plus redirects from old URLs to protect your search rankings.

Not directly — an APK is an Android package. If the game was made with an engine that supports web export (for example HTML5 or WebGL builds), we can create a browser version; otherwise it needs to be ported. We will tell you which applies after reviewing the project.

Yes, when they are designed for it: on-screen touch controls, responsive layouts and performance tuned for mobile hardware.

Yes. We add server-validated leaderboards, admin tools to reset or review scores and clear rules. Competitions with prizes must also follow local consumer and promotion regulations — we recommend a legal check of the rules.

We configure providers and contracts so that your data is not used for training where that option exists, and we explain each provider's terms before you decide. Sensitive workloads can also run on self-hosted models.

No AI is perfect, so we design for that: answers are grounded in your approved sources, show citations, admit uncertainty, and important actions require human confirmation. We also measure accuracy on a test set before launch.

It depends on volume and model choice. We estimate running costs per request during the proof of concept and use caching, smaller models and batching to keep them predictable.