We use Laravel 9.0 for developing new projects and also support our older projects on legacy frameworks such as Laravel 5+, we use only headless Content Management Systems like Netlify or Gatsby – i.e. no Wordpress, Joomla, etc.. We use NestJS for new projects and also support our older projects on NestJS and ExpressJS frameworks. We might use other frameworks or just different NodeJS modules, depending on the project requirements.
A good database is crucial to any company or organization. This is because the database stores all the pertinent details about the company such as employee records, transactional records, salary details etc. We use MySQL, PostgreSQL, MongoDB, Elasticsearch, Redis, InfluxDB, SQLite, etc.
Visual guide that represents the skeletal framework of a website, mobile application or extension. For wireframing we use Mockflow and Figma. "Colored wireframes" that depict what a website, mobile application or extension will look like. For mock-up-ing we use Photoshop, Sketch and Figma.
Virtually anything of value can be tracked and traded on a blockchain network, reducing risk and cutting costs for all involved. We use Blockchains, Ethereum/Polygon/Solana blockchains, Web3.js, ERC721 and ERC20 standards, Solidity.
With the right planning, you can ensure that your work is delivered on time and within budget. Using project management methods, you can map your project’s journey from the outset and know in advance where the deadlines — and projected spend — are going to fall, so you can more efficiently allocate your resources, helping you to avoid delays and project overspend.
APIs are needed to bring applications together in order to perform a designed function built around sharing data and executing pre-defined processes. They work as a middleman, allowing developers to build new programmatic interactions between the various applications people and businesses use on a daily basis. We use MailChimp, Stripe, PayPal, YouTube Data API, etc.
We perform manual testing and make heavy use of checklists, test cases and test plans. We also write unit and acceptance tests with a broad set of tools such as Selenium, Puppeteer, Protractor, Jest, etc. and do performance tests with Apache Benchmark, Jmeter and other tools.
We utilize different hosting services for our projects: AWS, GCP, Digital Ocean and Heroku. We use Docker and Docker Compose for local development.
We have experience with a broad set of AWS technologies and some GCP technologies. We use them if they fit into project requirements. AWS services we have expertise in: S3, VPC, EC2, EKS, OpsWorks, EBS, RDS, ElastiCache, CloudWatch, Route53, CloudFront, AWS Lambda (including serverless.com framework), AWS Elasticsearch, AWS Batch. GCP: Cloud Storage, GKE, Cloud SQL, Memorystore, BigQuery, etc.
We use Terraform as an IaaC tool, Ansible for server provisioning, Docker for containerization and CloudFront/Cloudflare as a CDN. Depending on the project requirements we use other technologies, for example: Letsencrypt, Memcache, RabbitMQ, etc.
Work Plan - Estimate
WPE (Work Plan - Estimate) - once we have a completed and approved PRD, you receive a Work Plan - Estimate with an accuracy of +/-20% for total hours and 3-5 days for deadline. Work Plan - Estimate will contain a detailed breakdown of the project as a whole into the 1-4 hour tasks.Learn more
Unlike working according to the WPE, we do not provide an estimate for a project or tasks. We allocate a full time team (40-45 hours for each member of the team). You get weekly reports on the hours spent from the internal redmine time tracking system, but at least a full 40 hours per team member must be used up each week. Otherwise the client pays for the full load regardless. The team is formed for projects with weekly load from 120 to 480 hours.Learn more