SystemsDK

FAQ

FAQ

Popular Questions

  • 1. What is your core expertise?

    We specialize in architecting and developing complex backend systems. Our primary focus is on building reliable, scalable, and high-performing solutions that act as a solid foundation for your business growth.

  • 2. Where is your team located?

    We operate as a global team with key locations in Kyiv, Ukraine and Munich, Germany.

  • 3. What is your technology stack?

    While the exact technology stack is tailored to specific project requirements, our foundation is built on PHP (Symfony, Laravel) and robust database expertise (Oracle, MySQL). We also heavily leverage Docker for infrastructure capability. For detailed examples, please refer to our Case Studies section or public GitHub repository.

  • 4. Where can I see code examples?

    You can explore our code standards and architectural approaches in our public GitHub repository. These examples are open-source and available for free usage.

  • 5. What are the infrastructure requirements?

    Our baseline requirement is a Linux environment (or WSL) running Docker and Docker Compose.
    Note: Specific requirements may vary depending on the solution selected. For detailed information, please refer to the relevant readme.md files in our GitHub repository.

  • 6. Do you provide documentation?

    Yes, all our solutions include essential documentation. You can find detailed setup instructions and usage guides within the relevant readme.md files in our GitHub repository.

  • 7. Do you offer post-launch support?

    You can communicate with us for support via our contact form or directly through email at support@systemsdk.com. Additionally, technical support for our open-source solutions is available via the "Issues" tab on our GitHub repository.

  • 8. Who owns the source code?

    We distinguish between the unique solution tailored to specific client needs and general open-source components or standard architectural patterns. Upon project completion and handover, ownership rights for the resulting custom application are intended for the client, while utilized frameworks remain under their respective licenses.

Interested in collaboration?

Discuss

Your Needs